The question is not which is bigger
Every version of this discussion starts with market share, and in India the answer is obvious: Android dominates by a wide margin. That single fact is also why the question gets answered badly, because it only tells you about reach and most startups are not reach-constrained in month one.
Three better questions: who exactly are your first thousand users, how will they pay you, and what does the app have to do that a website cannot?
Where each platform genuinely wins
Android first makes sense when:
- You are building for a mass Indian audience — delivery, local services, utility, education, agriculture, retail, anything tier-2 and beyond.
- Your users are price sensitive, which correlates strongly with Android in India.
- You need scale before monetisation, as with a marketplace that needs supply and demand.
- You want faster, cheaper iteration. Play releases ship in hours and staged rollouts let you expose a release to a small percentage first.
- Your users will side-load or arrive via a link; Android permits distribution paths iOS does not.
iOS first makes sense when:
- Your customers are high-spending urban professionals — premium health, finance, travel, luxury retail, executive services.
- Revenue per user matters more than user count, because iOS users in India spend more on average.
- You are selling to an organisation whose decision-makers use iPhones; the demo happens on their device.
- You depend on the camera, sensors or on-device processing working consistently, which is far simpler across a handful of iPhone models than across hundreds of Android devices.
- You are raising money from investors who will open it on an iPhone. Not a product reason, but an honest one.
The cost and timeline difference, plainly
Two native apps cost roughly twice one native app, because they share almost no code. That is the whole argument for cross-platform, and for a first version the argument usually wins.
- Cross-platform (Flutter or React Native): one codebase, both stores, typically 60 to 70 percent of the cost of building both natively. For most business apps, listings, bookings, dashboards and content, users cannot tell the difference.
- Native: the right choice for heavy graphics, intensive camera or sensor work, background processing, or when you need a brand-new platform API the moment it ships.
- Android testing is the hidden cost. Device fragmentation is real: an app that works on your phone can break on a budget device with a different Android skin and 2GB of RAM. Budget for a small device matrix rather than one test phone.
- iOS has a review tax. Every submission is reviewed by a person, rejections are common for first-time publishers, and each round costs days.
The underlying numbers for both routes are in our mobile app development cost in India guide, and the running cost that follows in app maintenance cost.
Publishing: what actually differs
- Fees. Google Play is a one-time 25 US dollar registration. Apple is 99 US dollars a year.
- Account type matters on Play. A personal developer account faces a closed-testing requirement before you can go to production, which adds weeks. An organisation account avoids it but needs company verification, and for an Indian private limited company that can mean producing a D-U-N-S number.
- Review time. Play is typically faster; Apple is slower and stricter, particularly on login requirements, payments and anything resembling a gambling or lending product.
- Declarations. Both stores require data-safety or privacy disclosures that must match what your app actually collects. Getting these wrong is a common rejection and an easy one to avoid.
- Staged rollout. Play lets you release to a percentage of users and halt. Useful enough that it changes how confidently you ship.
The full release sequence, including the traps, is in our Play Store and App Store publishing guide, and getting found afterwards is a separate discipline covered in the ASO guide for India.
The option most startups should consider first
Before either store: do you need an app at all this quarter? For a large share of Indian businesses the honest answer is no, and the money is better spent on a fast website plus WhatsApp.
- A website reaches everyone, with no install step. In India the install step is a real cost, because storage on a budget phone is genuinely scarce.
- WhatsApp is already installed. For ordering, support, reminders and follow-up, it beats an app nobody downloads. The comparison is laid out in mobile app or WhatsApp chatbot.
- A progressive web app covers part of the middle ground — installable, no store review, no download size. Its limits are explained in PWA versus native app.
An app earns its place when you have repeat users, something that must work offline, or a genuine need for device features. If none of those is true yet, building the app first means paying to discover what the cheaper route would have told you.
A decision you can make in five minutes
- Name your first thousand users. Not a demographic — an actual group you can reach. What phones do they hold? If you cannot answer, that is the research to do before the build.
- Decide how they pay. Free with ads or UPI payments points to Android. Subscriptions at a premium price point make iOS users disproportionately valuable.
- List the device features you truly need. Honestly. “Push notifications” is not a reason to go native.
- Pick cross-platform unless step 3 forces native. Then launch on the store your users are on, and release the second platform only once the first one shows retention.
- Keep the website working regardless. It is where everyone who has not installed your app will meet you, and it is the only version a Google search can find.
What changes after the first platform ships
The platform decision is usually treated as a one-off. It is actually the start of a sequence, and knowing the sequence changes the first choice.
- The second platform is cheaper than the first, but not free. Even with a shared codebase there is store setup, review, platform-specific bugs and a second set of crash reports. Budget perhaps a quarter of the original build, not nothing.
- Two platforms double the release overhead permanently. Every feature now ships twice and is reviewed twice. For a small team this is the real cost, and it recurs forever.
- Retention decides the timing. If people are not coming back on platform one, a second platform adds reach to a product that is not working yet.
- Keep one backend and one analytics setup. Teams that let the second app accumulate its own API quirks spend the following year paying for it.
Three questions that settle it faster than any comparison
- What phone is in the hand of the person who will pay you? Not your users in aggregate — the paying ones. For a subscription product those two groups can point at different platforms.
- Can you support two stores with the team you have today? If one developer is doing everything, two native apps is a commitment to slower releases on both.
- What happens if the app is rejected? On Apple that is a real possibility for a first-time publisher, and each round costs days. If your launch is tied to a date, that risk belongs in the plan rather than in the week of launch.
If the answers point in different directions, build cross-platform and launch on one store first. That keeps the second platform a decision rather than a commitment, and it is reversible — which the choice between two native codebases is not.
Frequently Asked Questions
Should an Indian startup build Android first?
For most Indian consumer products, yes, because the overwhelming majority of smartphone users here are on Android and reaching them is the point. The exceptions are products aimed at high-spending urban users, premium services, or anything where paid conversion matters more than reach, where iOS users are disproportionately valuable.
Is a cross-platform app a better answer than choosing?
Usually, for a first version. Flutter or React Native gives you both platforms from one codebase at roughly 60 to 70 percent of the cost of two native apps, and for most business and consumer apps the user cannot tell the difference. Go native when you depend on heavy device features, high-performance graphics, or the newest platform APIs on day one.
How much does publishing on each store cost?
Google Play charges a one-time 25 US dollar developer registration; Apple charges 99 US dollars a year. The bigger difference is process: Apple reviews every submission by hand with stricter rules, while Play review is faster but requires completed data safety declarations and, for personal accounts, a closed-testing period before production access.
Why does my Android app break on cheap phones when it works on mine?
Device fragmentation. Budget Android devices differ in RAM, screen density, manufacturer skin and OS version, and any of those can break a layout or exhaust memory. Test on a small matrix that includes at least one low-RAM device on an older Android version, rather than only on the developer’s phone.
Can I launch on both stores at the same time?
You can, with a cross-platform build, but it is often better not to. Launching on one store first means one set of reviews, one set of crash reports and one audience to learn from. Ship the second platform once the first shows people coming back.
Not sure whether your idea needs an app at all yet? Tell us what it has to do on WhatsApp and we will give you a straight answer, including if the answer is “not yet”.
Also read: budget the build with mobile app development cost in India, decide the simpler route in website or mobile app, and ship it properly with the publishing guide.
