The 60-second answer
- US-focused B2C app: launch iOS first. 58% of US smartphones run iOS, and iOS users generate ~2× the in-app revenue.
- EU-focused B2C app: it depends on your country mix. UK and Nordics → iOS first. Germany, France, Italy, Spain, Eastern EU → Android first or both at once.
- B2B app for SMB or enterprise: iOS first regardless of region. Decision-makers and SaaS buyers skew iOS.
- Logistics, fleet, last-mile, delivery driver apps: Android first. Industrial users are on Android, often on rugged or low-cost devices.
- Most modern teams should just go cross-platform and skip the "which first" question entirely. See our framework comparison.
The market share that actually matters
Total smartphone market share is the wrong metric. The right metric is "what percentage of your target users use which platform" — and that varies by country, income, age and use case.
United States (Q1 2026)
- Smartphone install base: 58% iOS, 42% Android.
- Users under 25: roughly 87% iOS. Teen iMessage / FaceTime lock-in is real.
- Household income above $100k/year: ~70% iOS.
- App Store revenue share of US consumer spend: ~65% iOS.
European Union (Q1 2026, country-weighted)
- UK: ~50% iOS, ~50% Android (London skews more iOS).
- Germany: ~35% iOS, ~65% Android — historically Android-heavy.
- France: ~28% iOS, ~72% Android.
- Italy: ~30% iOS, ~70% Android.
- Spain: ~22% iOS, ~78% Android.
- Nordics (SE, NO, DK, FI): ~55% iOS — iPhone is high-status and disposable income is high.
- Netherlands: ~55% iOS.
- Eastern EU (PL, RO, HU, BG, CZ, BAL): ~15–25% iOS, ~75–85% Android.
The "money follows iOS" rule still holds
Across both regions, iOS users out-spend Android users on apps by roughly 2.0–2.5× per active user. The gap is largest in:
- Consumer subscriptions (news, dating, fitness, language learning).
- Content and creator apps (paid features, tipping).
- Casual games with in-app purchases.
The gap collapses to near-zero in:
- Ride-sharing, food delivery, micromobility (users pay services, not the app).
- Banking and fintech (free tier, monetisation outside IAP).
- B2B apps invoiced per seat (you bill the company, not the user).
App Store vs Google Play in 2026: the operational differences
| Operational metric | App Store (iOS) | Google Play (Android) |
|---|---|---|
| Developer account fee | $99/year | $25 one-time |
| Median review time (2026) | ~24 hours | 24–48 hours (established), 3–7 days (new dev) |
| First-submission rejection rate | ~30% | ~12% (but slower fixes) |
| Standard commission | 15% (small biz) / 30%; EU 3rd-party billing allowed | 15% / 30%; EU 3rd-party billing allowed |
| Sideloading / alt stores | EU only (DMA) | Always allowed (APK) |
| OS fragmentation | Low (3 active majors) | High (test back to Android 10 in 2026) |
| Device fragmentation | ~30 models actively supported | ~1,500 active models |
What the EU Digital Markets Act actually changed
The DMA (in force since March 2024 for "gatekeepers") was supposed to break Apple's grip on iOS distribution in the EU. In practice, two years in, the picture is mixed:
- Alternative iOS app marketplaces (AltStore PAL, Setapp Mobile, Epic Games Store) exist but reach single-digit percent of EU iOS users. The App Store remains where ~95% of EU iOS users discover apps.
- Third-party billing in EU is the bigger change. You can route IAP through Stripe, Adyen or your own processor inside the EU and avoid Apple's commission (subject to Apple's "core technology fee" which mostly applies to apps at scale).
- Sideloading via web is permitted in EU; uptake is limited to enthusiasts.
Net effect on your "which first" decision: small. The DMA matters more to your monetisation than to your launch sequencing.
The hidden cost of "iOS only" or "Android only"
Founders often pick a single platform to save money, then discover the saving was smaller than the loss in addressable market. Some honest numbers:
- Building only iOS in the EU means missing 65–75% of the install base in DE, FR, IT, ES.
- Building only Android in the US means missing 65% of consumer app spend and likely all of your under-25 user base.
- Adding the second platform after launch is rarely free — your backend, design system, content rules and analytics get refactored to accommodate the second platform. Doing both at week one is 25–35% cheaper than doing them sequentially.
This is why cross-platform usually wins for a first build. See our cost ranges for cross-platform vs two-native in 2026 mobile app cost benchmarks.
Decision framework
Choose iOS first if
- Your primary market is the US, UK, Nordics, Netherlands or Switzerland.
- Your monetisation model is consumer subscriptions, content or premium IAP.
- Your target user is under 30 in any developed market.
- Your buyer is a corporate decision-maker (B2B SaaS extension app).
- You need TestFlight closed-beta speed during pre-launch.
Choose Android first if
- Your primary market is Germany, France, Italy, Spain, Eastern EU, Latin America, India or Africa.
- You ship to industrial / logistics / fleet users on rugged or company-issued devices.
- You sell at low ARPU and need volume (ad-supported, freemium with mass-market).
- You need to ship features Apple's review pipeline doesn't currently allow (sideloaded enterprise distribution, kernel-level networking outside EU DMA scope, etc.).
- You want fewer first-submission rejections during early iteration.
Choose cross-platform from day one if
- You have a single mobile team rather than two.
- You're aiming at both US and EU.
- You need to test demand before fully committing to either platform's deep features.
- You don't have a clear OS-specific technical reason (deep ARKit, Android Auto, kernel modules, CarPlay).
Case examples
- JoyJet — social platform, US + EU consumer market. Launched iOS and Android in parallel via cross-platform. iOS drove paid acquisition; Android drove organic growth.
- xRouten — German last-mile logistics. Android first (drivers on company-issued Android handhelds), iOS second once dispatcher tools went mobile.
- Signatory Pro — cross-border legal tech for lawyers. Native iOS first (clients on iPhone), Android shortly after for paralegals in EU.
- LiMP — consumer privacy app, EU + US. Both platforms day one; near-equal install split.
FAQ
Should I launch on iOS or Android first in 2026?
For the US and English-speaking Europe, iOS first. For continental EU (DE/FR/IT/ES) and Eastern EU, Android first. For most teams, cross-platform on day one is the right answer.
What is the iOS vs Android market share in the US and EU in 2026?
US: ~58% iOS, ~42% Android. Western Europe: ~33% iOS, ~67% Android with significant country variance (UK ~50/50, Germany ~35/65, Nordics ~55/45).
Is App Store or Google Play review faster?
App Store is faster median (~24h) but has higher first-submission rejection (~30%). Google Play is slower for new developers (3–7 days) and faster for established ones (24–48h).
Does the EU DMA change which platform to launch first?
Slightly. Alternative iOS marketplaces have low adoption. The DMA's bigger impact is third-party billing in the EU, which affects monetisation more than sequencing.
Do iOS users actually spend more?
Yes — global IAP ARPU on iOS is ~2.0–2.5× Android. The gap is largest in subscriptions and content, near-zero in marketplaces and B2B.
Can I just launch on both platforms at once?
Yes, and for most apps this is the right call. Cross-platform launches both stores in roughly the same time as one native build.
Talk to engineers, not salespeople
We help US and EU teams decide platform sequencing in a 30-minute call — based on your target geography, monetisation model and team — not a pitch deck.
Last updated 21 May 2026. Market share numbers from Statcounter Q1 2026 averages. Revenue and ARPU numbers cross-referenced with Sensor Tower and data.ai 2026 reports.
