Skip to content
Vijay Gojiya
How I work

Hire me

Hire a mobile app developer

One person who takes an idea to an app on both stores, including the native layer and the release.

Most mobile projects fail somewhere between the build being finished and the app being available, and the reason is that building and shipping are treated as the same skill. They are not. Signing, provisioning, privacy declarations, data safety forms, screenshots, phased rollout and a review team that rejects on metadata are their own discipline, and I have been through them enough times that they are routine.

What you get is an app on both stores under your own developer accounts, a typed codebase your next developer can read, and a release pipeline you can run without me. I build for iOS and Android at the same time from one React Native codebase, and I write the Kotlin and Swift myself when the app needs it.

What that covers

  • iOS and Android together, from one codebase
  • Store setup, signing and first submission under your accounts
  • Payments, push, deep links, offline and the other awkward requirements
  • Analytics and crash reporting wired to something someone reads
  • Handover documentation written for the developer after me

I do not do brand identity or marketing sites as standalone work. I will implement a designer Figma properly; I would rather not invent your logo.

How it would be billed

  • Fixed-price project

    A scoped piece of work, quoted after discovery and billed against milestones. Best when you know what you want built.

  • Monthly retainer

    An agreed number of days each month, billed in advance. Best when the work is continuous and the priorities move.

  • Consulting and audit

    A fixed number of days ending in a written document. Best when you need an answer rather than a developer.

  • Inside your team

    A day rate, your process, your standups, your repository. Best when you have a team and need one more senior pair of hands.

Work that backs this

Questions

Do we need separate developers for iOS and Android?

Not with React Native, which is most of the point. One codebase produces both apps, one feature gets built once, and the places where the platforms genuinely differ are handled deliberately rather than duplicated by accident.

Who owns the code and the accounts?

You do, from the beginning. The repository is yours, the developer accounts are in your organisation, the signing keys are in your custody and the third-party services are billed to you. I have seen what happens when an agency holds the keys, and I do not want to be that story.

What happens after launch?

Either you take it on with the documentation and pipeline I leave, or I stay on a monthly retainer for maintenance, store updates and small features. Both are normal. The first one is the one I design for.

Also hiring for a Expo developer?

Still the right person?

A sentence about the product and where it is stuck is enough to start. I answer every mail myself, including the ones where the answer is that I am not the right person.