iOS, Android or Both? Launching a Mobile App in 30 Days

Launch on both iOS and Android with one cross-platform codebase unless your app depends on heavy graphics, AR or constant background work. Worldwide, Android has 69% of phones; in the US, iPhones have 54%, so one platform leaves out a big group either way. A focused cross-platform app can reach both stores in about 30 days, if you plan for Google's 14-day testing rule.

Disclosure: I run Ship It Live, a fixed-price design and development service, so I have a stake in this topic. Every number below links to its source; the build stories are from my own products, not client work.

Should you launch on iOS, Android or both?

Start from where your users are, then ask what one platform would cost you. The split is very different depending on the market:

Market	iOS share	Android share	Source
Worldwide	30.81%	69.17%	StatCounter, September 2026
United States	53.59%	46.39%	StatCounter, September 2026

In the US the market is close to even, so an iOS-only launch reaches about half of phones. Outside the US, Android dominates, and an iPhone-only app misses most people.

One platform is still the right call in a few cases:

• Your audience is almost all on one platform, for example an internal app for a team that's issued iPhones.
• The app depends on platform-specific features, such as deep Apple Watch or HealthKit use, where the other platform would be a different product.
• You're testing demand with a tiny budget and would rather learn on one platform first.

If none of those apply, launching on both usually costs little extra with a cross-platform framework.

Is one codebase good enough in 2026?

For most apps, yes. Frameworks like React Native, which we use, render real native components, not a web page in a wrapper. Users can't tell the difference in a typical app built from lists, forms, feeds, maps, payments and notifications.

Where native code is still the honest answer:

• Heavy graphics, games and AR, where every millisecond of rendering matters.
• Sustained background processing, such as continuous location tracking or audio, where native code gets more control from the operating system.
• Apps that are mostly a single platform-specific feature.

We moved one of my own apps, Cafeity, from a native iOS codebase to Expo (React Native) while it was live with real users. The move gave it one codebase for both platforms and over-the-air updates for fixes that don't touch native code. Before switching, we compared the old and new builds behaviour by behaviour, across 30 categories, so that updating didn't break anyone's data or habits.

How long does it take to launch a mobile app?

A focused cross-platform app can be designed, built and submitted to both stores in about 30 days. The store reviews themselves are faster than most people expect, with one important exception.

Apple: Apple says that, on average, 90% of submissions are reviewed in less than 24 hours. First submissions and apps in sensitive categories can take longer.

Google: if you publish from a new personal developer account (created after 13 November 2023), Google requires a closed test with at least 12 testers who stay opted in for 14 days before you can apply for production access. Organisation accounts don't have this rule. Plan for it on day one, or your Android launch will trail your iOS launch by two weeks.

This is how our mobile app in 30 days sprint runs, for a fixed $2,500:

Days	Stage	What happens
1–3	Scope lock	One feature list for both platforms; anything platform-specific is decided now
4–12	Design	Screens designed once and checked against both platforms' conventions
13–24	Build	One codebase, both targets; test builds on TestFlight and Play's testing track around day 21
25–28	Two-platform testing	Real devices on both sides
29–30	Submit to both	Store listings finished and both builds submitted

What does a launch-ready mobile app need?

More than screens. A version-one app that's ready for real users includes:

1. Sign-up and login, including password reset and account deletion, which Apple requires for apps that let you create an account.
2. The core workflow, with empty, loading and error states designed, not just the happy path.
3. Push notifications that the user has a reason to allow.
4. Crash reporting and analytics, so you see problems before your reviews do.
5. Store listings: screenshots, a description and a privacy declaration that matches what the app actually collects.
6. A way to ship fixes fast. Over-the-air updates handle JavaScript-only fixes; anything native needs a new store build.

What does a mobile app cost to run after launch?

Less than most founders expect, before you count your backend. The store fees are published:

Cost	Published price	Source
Apple Developer Program	99 USD per membership year	Apple Developer
App Store commission on digital sales	30%, or 15% in the App Store Small Business Program	Apple Developer
Google Play developer registration	25 USD, one time	Play Console Help
Google Play service fee	Depends on the product and your earnings	Play Console Help

Commissions apply to digital goods and subscriptions sold inside the app. Physical goods and services, such as a ride, a booking or a delivery, are paid through normal payment processors instead.

The bigger running costs are usually your backend (database, authentication, file storage), push notifications at scale, and any AI or mapping APIs the app calls. Most start on free or low-cost tiers and grow with usage. Budget for one more thing: keeping up with yearly iOS and Android releases, which occasionally need small code changes.

What usually delays a mobile launch?

Rarely the code. These are the usual causes:

• Store rejections for missing basics: no account deletion, a broken demo login for the reviewer, or a privacy label that doesn't match the app.
• Late platform surprises: a feature that works on iOS but needs a different approach on Android, discovered in week four instead of day two.
• Google's 14-day closed test, started too late.
• Content arriving late: copy, icons and screenshots that nobody owned.

All four are planning problems, which is why the first three days lock the scope for both platforms before design starts. If you only need one platform, there are separate iOS and Android sprints at the same price.

Sources checked on 8 October 2026: StatCounter Global Stats (September 2026), Apple Developer App Review page, and Google Play Console Help on testing requirements for new personal developer accounts. Questions? Talk to the Ship It Live team.