Mobile App Development Company in Mumbai

Scope, and cut

We need from you. An hour with whoever will actually use the app. Not only whoever is paying for it

You get. A written scope, a screen list, and the three features we would leave for version two

A prototype you can tap

We need from you. Feedback within two days on each round

You get. A clickable prototype on your own phone. You will change your mind about checkout here — far cheaper than changing it in week nine

Build, in two-week sprints

We need from you. One person who can answer questions the same day

You get. A working build installed on your phone at the end of every sprint. Not a status report. The app

Test on real devices

We need from you. Two or three of your staff trying to break it

You get. Tested on the budget Android your customers actually own, not only the flagship we develop on

Stores, and the first rejection

We need from you. Google Play and Apple developer accounts in your company’s name

You get. Listing, screenshots, privacy forms, submission — and the first review rejection handled. There is usually one

Keep it running

We need from you. Nothing, unless you want new features

You get. Crash monitoring from day one, a named engineer on WhatsApp, and fixes before Apple’s September OS release breaks something small

Whose name are the store accounts in?

If the app is published under the agency’s developer account, you don’t fully own it. Moving it later is painful, sometimes impossible. This one question disqualifies more agencies than any other.

Can I install something you built?

Not a portfolio PDF. An app, from the store, on your phone, that you tap through during the call.

Who builds it — you, or someone you hand it to?

The people on the sales call and the people writing the code are often different companies. Ask to meet the engineer.

Which phones do you test on?

If the answer is the latest iPhone and a Pixel, your customers on budget Androids will find the bugs for you.

What happens when Apple rejects it?

It will, probably once. You want someone who has handled that before and has already budgeted the time for it.

Who fixes it in month four?

A named person on WhatsApp, or a ticket queue. Ask how fast they reply on a Saturday.

Why that framework?

If every project gets the same answer, you’re hearing what their team knows, not what your app needs.

Eight to twelve weeks for a focused first version: one type of user, one core flow, one way to pay. Add a second user type — a delivery partner, a vendor, a technician — and it moves closer to sixteen. The part people forget to plan for is the store. Apple review takes anywhere from a day to a week, and the first rejection is usually about something small, like a sign-up screen with no way to delete the account.

It depends on scope, and we quote after scoping rather than before. What moves the number: one platform or both, how many types of user the app has, how many outside systems it talks to (payments, your ERP, a courier API), whether it needs a custom backend and admin panel or one already exists, offline use, and how custom the design is. What does not move it: the number of people who download it. There is no per-user licence. You own the app.

Android, for most Mumbai businesses. More than nine in ten smartphones in India run it. The exception is a premium consumer brand, where iOS share among your actual buyers can be far higher than the national number — check your website analytics before deciding. Or skip the choice. Flutter and React Native ship both from one codebase, which is how we built the D2C app on this page.

None of them is better in general. Flutter when the design has to look identical on every phone and there is no existing web codebase. React Native when you already run a React website and want to share logic and engineers with it. Native Kotlin and Swift when the app lives on hardware — Bluetooth printers, barcode scanners, background location. If an agency gives the same answer for every project, you are hearing what their team knows.

Yes, both, from day one. The code sits in a repository in your name. The Play Console and App Store Connect accounts are registered to your company, not ours — we are added as developers and removed whenever you like. Ask every agency this question. An app published under the agency’s developer account cannot simply be moved later, and that is exactly how clients get stuck.

Usually, yes. We start with a one-to-two week code audit and tell you plainly whether to continue on what exists or rebuild the parts that are holding it back. Sometimes it is fine and just needs an owner. Sometimes the backend is fine and the app is the problem. The one situation we cannot fix quickly is an app published under the previous agency’s store account — so check that first.

Yes. Store listing, screenshots, privacy disclosures, the data-safety form on Google Play, submission, and the back-and-forth with review. We budget time for one rejection on iOS because there usually is one. You need a Google Play developer account and an Apple developer account in your company’s name, and we walk you through setting both up if you have not.

Crash reporting is switched on before launch, so we usually know about a bug before your customers do. After that it is a monthly retainer or on-call fixes, your choice, with a named engineer you can message on WhatsApp rather than a ticket queue. Plan for one piece of work every year regardless: Apple and Google both ship major OS updates, Apple every September, and something small always needs adjusting.

Yes, and it is a large part of the rest of our work. Search that understands what a customer means rather than the exact product name, a support assistant that answers from your own catalogue and policies, voice input in Hindi and Marathi, document or photo reading in field apps. We are specific about what runs on the phone, what runs on your server, and what — if anything — goes to an outside model.

Yes, before the first call if you want. The D2C case study on this page is anonymised for exactly that reason — the client asked us not to name them, so we do not. Your idea is not the valuable part to steal, honestly. The execution is. But we understand why you would want it on paper.

Yes. Nexona is registered in Mumbai and works across the MMR. Thane and Navi Mumbai are markets we serve, not offices we claim. Scoping can happen in person at your office; the build itself is remote, the way it is for most engineering teams in this city. Ask anyone you shortlist for the address on their GST registration. It takes thirty seconds and it tells you a lot.