If your budget doesn't stretch to both platforms at once, you need to pick one. Here's how to think through that decision without getting lost in opinion.

It's one of the most common questions we get from clients who are planning their first app. The honest answer is: it depends on your users. But that's not very useful on its own, so here's the full picture.

The market reality in Australia

Australia skews iOS. Depending on the source and year, iPhone typically accounts for around 55–60% of Australian smartphone market share, with Android making up the rest. That's a significant majority — but Android's 40–45% is still a substantial audience, and in some demographics and regions it's considerably higher.

The global picture is different. Android dominates internationally — roughly 70% market share worldwide. If your app has international aspirations, that matters.

Who are your users?

Before the market statistics, ask yourself: who's actually going to use this app?

Demographics where iPhone is stronger:

Urban professionals
Higher-income earners
Younger adults (18–34) in metro areas
Healthcare and professional services clients

Demographics where Android is stronger:

Regional and rural areas
Trades and labour-intensive industries
Lower price-sensitive demographics
International markets (especially Southeast Asia)

If your business is in the Southern Highlands and your customers are local tradespeople, the Android proportion among your users might be higher than the national average. If you're targeting Sydney professionals, the iPhone proportion probably is too.

The most useful data point is what your existing customers are using. If you have a database of clients, or can ask a sample, do it. A 10-minute survey before you start development is worth more than any market statistic.

Internal vs customer-facing apps

If this is an app for your own staff — not for customers — the calculation is different.

For internal tools, you control the hardware. You can simply decide what devices your team uses and build for that. This is often how businesses building a first internal app end up going iOS — because the decision-maker has an iPhone and has already bought iPhones for the team.

For customer-facing apps, you don't control the hardware, and you need to meet your users where they are.

What does "building for one platform" actually cost?

Building a quality native app for one platform (iOS or Android) is meaningfully cheaper than building for both. The design and backend work is shared — so you're not doubling the cost — but the native development work is platform-specific.

A rough rule of thumb: a dual-platform native app costs roughly 60–70% more than a single-platform app, not double. So if iOS alone might cost $40,000, iOS + Android might be $65,000–$70,000.

Cross-platform tools like React Native let you share a single codebase across both platforms, which can reduce that premium. It's a good option for many apps — but it has trade-offs in performance and access to platform-specific features, and isn't always the right call for complex apps.

The sequencing argument

A common approach for budget-conscious launches:

Build for iOS first (since it's the majority in Australia and tends to be faster to deploy due to more consistent hardware)
Gather real user feedback
Build Android — now informed by what you learned

This works well when your target audience skews iOS and you need to validate the concept before investing in the second platform. The risk is that you lock out a significant portion of your potential users at launch.

The opposite approach — Android first — makes more sense if your users skew Android, or if you're planning international expansion.

When you should build for both at once

Your users are split roughly evenly between platforms
You're building a consumer app that needs critical mass from day one
The nature of the app means word-of-mouth matters and you can't afford to exclude half your potential users
You're using React Native anyway, where the marginal cost of the second platform is much lower

The React Native option

React Native, developed by Meta and used widely in industry, lets you write most of your app code once and deploy it to both iOS and Android. At Code Workshop we use it for a significant portion of our mobile work.

It's not right for everything. Apps with demanding graphics, custom animations, or deep integration with platform-specific hardware (camera, sensors, Bluetooth) often work better native. But for most business apps — forms, data display, user accounts, notifications, integrations — React Native produces excellent results at lower cost.

If you're torn between platforms because of budget, this is often the answer: build cross-platform from the start, spend roughly what you'd spend on one native platform, and cover both.

Our recommendation

If we had to generalise: for most Australian small businesses launching their first customer-facing app, we'd suggest:

Start with iOS if your users are likely to be in the 55%+ iPhone majority
Consider React Native if budget is the primary constraint and you want both
Run a quick survey of your existing customers before making the call

The worst outcome is spending months in analysis paralysis. Pick a platform, build something real, and iterate.

If you'd like to talk through the right approach for your specific situation, we're based in Bowral, Southern Highlands, NSW and happy to have a no-obligation conversation. It often only takes half an hour to get to a clear answer.