Launch first on the platform your paying customers actually use. In India, that usually means Android; in Australia, the USA and much of Western Europe, iOS often matters as much or more, especially for apps that charge users. If you're building cross-platform with Flutter or React Native, launching on both at once is usually the smarter, only slightly costlier option.
Does the choice still matter if you build cross-platform?
Much less than it used to. With one shared codebase, adding the second platform is mostly extra testing, design polish and store setup rather than a second build.
The "pick one first" question really applies in three situations:
- You're building native apps, so each platform is a separate project and budget.
- Your budget is so tight that even the extra testing and store work has to wait.
- You want to validate demand with one audience before investing in the other.
If none of these apply, launch on both. You'll avoid frustrating half your audience with a "coming soon" message. Our comparison of native vs cross-platform development, including Flutter vs React Native explains why cross-platform is the default for most business apps.
Where are your users, really?
Your own data beats national averages every time. Check it before reading any market statistics.
Three free ways to find your split:
- Website analytics. Look at mobile visitors by operating system over the last six to twelve months. This is the single best predictor for most businesses.
- Customer conversations. Ask your sales or front-desk team which phones customers hold up when booking or paying.
- A short survey. One question in a post-purchase email ("Which phone do you use?") gives you a direct answer.
As general background, without relying on any specific figures:
- India: Android phones dominate the overall market across most price points, so an Android-first launch reaches far more people.
- Australia, the USA, the UK and Canada: iPhones hold a large share, and iPhone owners have historically been more willing to spend inside apps.
- Business buyers: often skew towards iPhones in some professional sectors, while field and frontline teams frequently use Android, including rugged devices.
If your analytics show a clear majority on one platform, start there; if the split is close, launch on both.
How does your revenue model change the answer?
If users pay inside the app, revenue per user matters as much as user numbers. If the app supports an offline business, reach matters more.
| Revenue model | What to prioritise | Typical lean |
|---|---|---|
| Subscriptions or in-app purchases | Users most likely to pay | iOS often first in AU, US and Western Europe |
| Ad-supported | Largest audience | Android often first, especially in India |
| Supports a physical business (bookings, orders, loyalty) | Matching your existing customers | Follow your website analytics |
| Staff or field app | Devices your team carries or you issue | Whatever you provide; Android is common for company-issued devices |
| B2B client portal | Your clients' devices | Ask your top accounts directly |
Remember that digital goods and subscriptions sold inside apps generally go through Apple's and Google's billing systems, with commission typically in the 15–30% range depending on the programme. Physical goods and real-world services can usually use your own payment provider.
How do development and testing differ between the platforms?
iOS is quicker to test because there are fewer device models; Android takes more testing because of the variety of phones. Both need real-device testing before launch.
Practical differences:
- Device variety. Android runs on thousands of models from many manufacturers, with different screen sizes, chips and customised software. Testing on a few popular and older mid-range phones is essential.
- Build tools. Building and submitting iOS apps requires a Mac and an Apple Developer account. Android builds can be produced on any major operating system.
- Beta testing. Apple uses TestFlight; Google Play offers internal, closed and open testing tracks.
- OS updates. iPhone users tend to adopt new iOS versions quickly, so you can support fewer old versions. Android users are spread across more versions, so you'll often support older ones longer.
None of this should decide your launch platform on its own, but it affects timelines. Our guide to how long a mobile app takes to build includes testing and store submission in its phase estimates.
What about App Store and Google Play review?
Apple's review is generally stricter and more likely to send a first submission back; Google Play has its own testing requirements for new developers. Build time for both into your plan.
- Apple reviews every submission against its App Review Guidelines. Common rejections include crashes, incomplete features, missing reviewer login details, and apps that add little beyond a website.
- Google Play reviews apps too, and requires new personal developer accounts to run a closed test with real testers before releasing to production. Organisation accounts have different requirements, so register under your business where you can.
- Both stores require privacy disclosures (Apple's privacy labels and Google's Data safety section) and expect in-app account deletion when users can create accounts.
- Fees: Apple's Developer Program costs US$99 a year; Google Play charges a one-off US$25 registration.
Plan one to two weeks for store setup, review and any resubmission, whichever platform goes first.
What are the risks of launching on only one platform?
You may frustrate or lose customers on the other platform, and some never come back. Plan the gap deliberately.
Risks:
- Customers on the missing platform feel excluded and may leave poor reviews or choose a competitor.
- Marketing gets awkward: every ad and social post must explain which phones are supported.
- Product decisions get skewed towards one audience's behaviour.
Ways to soften the gap:
- Offer a mobile website or progressive web app with core features for the other platform.
- Collect a waitlist with email or WhatsApp opt-in, and announce the launch when ready.
- Set a firm date for the second platform, ideally within weeks rather than months.
A practical decision framework
Answer four questions in order; the first clear answer usually decides it.
- Are you building cross-platform? If yes and budget allows, launch both. Stop here.
- Does your own data show a clear majority on one platform? If yes, start there.
- Do users pay inside the app? If yes and you're targeting Australia, the USA or Western Europe, iOS often comes first.
- Is it a staff or B2B app? Follow the devices your team or clients actually use.
If you're still undecided after that, the split is close enough that launching both is worth the extra effort. For a broader view of planning, costs and launch, our complete guide to mobile app development in 2026 brings it all together, and our AUD guide to app development costs in Australia covers budgets for Australian projects.
Frequently asked questions
Is it cheaper to launch on Android or iOS first?
With native development, costs are broadly similar per platform, though Android may need more device testing. With cross-platform development, launching on both costs only moderately more than one. The bigger saving comes from narrowing features, not platforms.
Should Indian startups always go Android-first?
Usually, if the goal is reach, because Android dominates the Indian market. But if your target customers are premium buyers or the app depends on in-app purchases, check your own data; iOS can matter more for some audiences than national averages suggest.
How long after launching on one platform should we release the other?
If you're using cross-platform code, aim for weeks, not months. A long gap risks losing early customers on the missing platform. With native apps, plan the second platform's budget and timeline before the first one launches.
Can we test demand without launching on either store?
Yes. A clickable prototype, a landing page with a waitlist, or a progressive web app can all validate interest before you commit to store releases. This is often the cheapest way to answer the platform question with real data.
Does Apple's stricter review mean we should launch on Android first?
Not on its own. Review strictness affects your timeline by days or a couple of weeks, not your long-term success. Choose based on where your customers are and how the app earns money, then build review time into the plan.
Get a launch plan built around your customers
GRWW helps businesses plan, build and launch apps on the platforms their customers use, alongside the websites and systems behind them; explore our services. If you'd like help deciding, ask for a fixed-price quote and launch plan and bring your analytics; we'll read them with you.