Decision guide · 6 min read

iOS, Android, or both? A small-business owner's guide.

"Do I need iOS and Android?" is the most expensive question in app development. Get it wrong and you double your build cost for no return. Get it right and you ship faster, for less.

By · · Pick the right platform without overspending

Most small businesses don't need both — at first

If you have under 1,000 users at launch and a roughly typical Australian demographic, your audience is probably ~55% iOS, ~45% Android. That feels like "need both" — until you remember that almost all of them have a phone and use a browser.

For most small businesses, the right answer in 2025 is: a great web app first, with native mobile added when you have the user base to justify it.

The four scenarios

1. Web-first (most B2B + service businesses)

Bookings, orders, dashboards, internal tools, professional services. Works on every device, no install friction, no App Store gate. Build a web app, skip native entirely at launch.

2. Mobile-first cross-platform (most B2C)

Consumer apps where push notifications + camera + native feel matter. Build one codebase with React Native or Flutter, deploy to both iOS and Android. One developer, one timeline, one budget — two stores.

3. One platform native (rare but valid)

You have a strong, measurable iOS-heavy or Android-heavy customer base, and you need platform-specific features (Apple Watch, Wear OS, deep ARKit, etc.).

4. Both fully native (very rare for SMB)

Reserved for apps where mobile is the entire business and the budget supports two specialist teams.

Why cross-platform is the small-business default

React Native and Flutter today share 90%+ of code between iOS and Android while still producing real native binaries. For 95% of small-business apps your users genuinely cannot tell the difference.

What you save: roughly half the development time and half the ongoing maintenance. What you give up: a small number of bleeding-edge platform features you probably weren't going to use anyway.

A two-question decision framework

  1. Do my users need to install the app, or would a web link work? If a link works, build web first.
  2. If I had to pick only one of iOS or Android, would I lose more than 30% of my audience? If no, ship one. If yes, use a cross-platform framework and ship both for one budget.

Common (expensive) mistakes

  • Building native iOS + native Android in parallel when you don't have enterprise budget. You're paying twice for no real upside.
  • Skipping web entirely for an app most users would have just opened in a browser.
  • Choosing platform based on the founder's phone. Your phone is not your audience.

Thinking about your own app?

Send Charlotte a one-sentence postcard about what you're building. She reads every one personally — usually replies within a day.

Send a postcard →

FAQs

Is React Native or Flutter "as good as" native?
For 95% of small business use-cases, yes. Both produce real native binaries with native UI components. The remaining 5% (very heavy 3D, low-level audio, latest ARKit features) genuinely benefit from native.
Will I need to rebuild later if I start with web only?
Not necessarily. Many businesses run on a great web app for years. If demand for a native app emerges, it can be added without throwing away the web app — both can coexist with a shared backend.
Does Apple's 30% cut apply if I build a custom app?
Only if you sell digital goods/services through the App Store. Physical products, services, and external SaaS sign-ups are exempt. Worth checking before you decide.
Can one developer really build for both iOS and Android?
Yes — with React Native or Flutter, that's the entire point. One developer, one codebase, two stores.