The default answer to "iOS or Android?" is "both, please". We frequently push back on that. Building for two platforms simultaneously isn't always wrong, but it isn't always right either, and the cost is real.
Here's the framework we use with clients to pick deliberately.
Where the money goes
Two platforms cost roughly 1.5–2× one platform. That's true even with cross-platform tooling like React Native or Flutter, because:
- Every screen needs platform-specific polish to feel native (haptics, transitions, keyboard handling, accessibility).
- Each app store has its own review process, listing optimisation, and ongoing compliance overhead.
- Push notifications, deep linking, biometric auth, and in-app purchases work differently enough on each platform to need parallel work.
- You're testing every change on twice as many devices, OS versions, and form factors.
If your budget is tight, picking one platform first is usually the smart move.
Australia's market shape
The Australian mobile market sits roughly 55/45 iOS to Android (Statcounter's most recent data; varies by quarter). But that aggregate hides what matters: the split is sharply demographic.
- iOS skews higher-income, urban, and younger working professionals. Strong in Sydney, Melbourne CBD, and inner-suburban areas.
- Android skews wider — more representative across income, age, and geography. Stronger in regional, in trades, and in field-services roles.
If your customer base concentrates in one of those, the platform decision largely makes itself.
Five questions to ask
1. Where is your audience?
Survey your actual users (or use existing analytics if you have a web product). If 80%+ are on one platform, start there.
2. What's the user journey?
If your users discover you on web and then download an app to deepen the relationship, look at the platforms your existing web users carry. If your users discover you in the app store, you need wherever they search — usually both, but iOS first if your category skews professional.
3. What's the device dependence?
Some features behave dramatically differently across iOS and Android. Camera-heavy apps benefit from iOS's stricter hardware consistency. Background processing favours Android. Hardware integrations (NFC, Bluetooth, sensors) need careful platform-by-platform testing.
4. What's the payment story?
Apple takes a 15–30% cut on in-app purchases. Google takes the same. If your business model depends on in-app revenue, the platform choice has direct margin implications, and the app store policies are getting tighter rather than looser. Apple's recent EU concessions have not (yet) extended to Australia.
5. What's your iteration speed?
Apple's review process is slower than Google's. If you're pushing weekly releases with rapid experimentation, iOS will frustrate you. Android lets you iterate faster on the app side, though TestFlight has narrowed the gap on iOS.
Three patterns we recommend
"iOS first, Android six months later"
Common for B2B and premium consumer apps. Build the iOS version, get it right, validate the product with real users, then bring Android online with the lessons learned. Cheaper than parallel and produces a better product.
"Android first, iOS later"
Less common but right when your audience skews regional, trades, or international (especially Asia-Pacific outside Australia). Some of our utilities-sector clients have gone this route because the field workforce is Android-heavy.
"Both at once, native each"
The "premium" option. Right when budget allows, the customer base is genuinely split, and the product is critical enough that both platforms need to feel first-class from day one. Costs roughly 1.8–2× single-platform.
What about cross-platform?
React Native, Flutter, and Kotlin Multiplatform are good and getting better. We use all three, depending on the project.
Cross-platform is the right answer when:
- The UI is largely standard (forms, lists, navigation, payment flows)
- Performance is good enough at "very good" rather than "perfect"
- The team is sized to maintain a single codebase, not two
Cross-platform is the wrong answer when:
- The app is heavily hardware-integrated
- You need bleeding-edge platform features the day they ship
- The UX is the product, and you can feel the cross-platform-ness in your bones
The fastest version of this decision
If you want a ten-second answer: most Australian businesses building their first product app should start with iOS in Sydney/Melbourne, expand to Android in 6–12 months. If your customer base is field, regional, or trades, flip that. If you're well-funded and your audience is genuinely 50/50, build both at once and use a cross-platform framework unless you have a specific reason not to.
If you'd like a senior team's view on your specific situation, book a discovery call.
