iOS or Android First? How to Pick for an MVP
iOS first if your buyers are in the US, UK, EU, or Japan. Android first if they aren't. Need both on one budget? One React Native repo, not two native teams.
Table of Contents
Build iOS first if the people who will pay you live in the US, UK, EU, or Japan. Build Android first if they live where Android is most of the phones in their pocket. If you need both and you have one sprint of budget, do not pick a favorite phone. Ship both from one React Native codebase. If the job happens at a desk, build neither yet. Build the web app.
Ready to build?
Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.
Pick from your first 100 users, not from a chart
Global market share says Android. US consumer spend says iOS. Both stats are true and neither is your customer list. Write down where the first hundred people are, what phone they reply to you from, and whether they pay for apps today. A fitness app for US gyms and a delivery app for a city in Latin America are opposite answers. "I have an iPhone" is not a market.
When iOS is the right first store
Paid consumer apps, subscriptions, and audiences who already spend on the App Store. You will also meet a stricter review: demo login, in-app purchase for digital goods, and a complete loop. Budget the review time on top of the build. Two days is normal for a clean submission. A week is normal for a first app. The App Store review breakdown is the calendar, not a guess.
Want us to build it?
Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.
When Android is the right first store
Price-sensitive markets, field teams on cheaper devices, and products where WhatsApp and Android are the default. A new personal Play Console account still owes you 14 days of closed testing with 12 testers before production. An organisation account skips that gate. Either way, test on a mid-range phone. A layout that only works on a flagship will get you one-star reviews from the people you built for.
When the answer is both, or neither
Both: React Native and Expo, one repo, TypeScript if you also have a Next.js site. Two native teams doubles the invoice and the bugs. Neither: the user is at a laptop, you care about Google, or the "app" is a dashboard. A store listing is a distribution channel, not a quality badge. Our platform guide walks the same decision from the product side, including the case where mobile is v2.
- Desk workflow or SEO: web first
- Camera, push, or the stores are the product: mobile
- Both stores, one budget: React Native, not Swift plus Kotlin
- A webview submitted as an app: expect a 4.2 rejection on Apple
Ready to build yours?
Fixed-price web and mobile MVPs from $3,460. Book a call or WhatsApp us.
Questions
Should I build iOS or Android first?
iOS first if your first customers pay in the US, UK, EU, or Japan. Android first if they are in markets where Android is most of the phones. If you need both and the budget is one sprint, use React Native and ship both from one repo.
Which store makes more money?
In the US and similar markets, iOS users spend more per person. Worldwide, Android has more phones. Pick from where your first 100 users actually are, not from a global market-share chart.
Should a B2B product start on mobile at all?
Usually no. If the job happens at a desk, ship a web app first. Add a store app when camera, push, or offline is the product.
Is a website wrapped in a store shell an iOS app?
Apple often rejects thin wrappers under guideline 4.2. If the app is a website in a webview, you do not have an iOS product yet.
Related Articles
- App Store Review Time in 2026: 48 Hours for 90%
- PWA vs Native App in 2026: Which to Ship First
- How to Get Your First 100 App Users (No Ads)
- Do You Need an NDA Before Sharing an App Idea?
Ready to ship your MVP?
Fixed-price builds from $3,460 · Post-launch support from $500/mo
From Build MVP Fast