Native or cross-platform for a small business app
When one codebase for iOS and Android is the right call, when native genuinely wins, and why the choice matters less than people argue.
This argument runs hot among developers and matters far less than it seems from the outside. For most small business apps, either approach produces something your users cannot tell apart, and the decision should be made on cost and staffing rather than on principle.
Here is the version without the tribalism.
What the choice actually is
Native means writing the app twice: once in Swift for iOS, once in Kotlin for Android. Two codebases, two skill sets, every feature built twice.
Cross-platform means one codebase producing both apps. React Native and Flutter are the two that matter. The interface is described once and rendered on both platforms.
The old objection was that cross-platform apps felt wrong: slow, janky, visibly not native. That was a fair criticism a decade ago and is mostly no longer true for the kind of app a small business builds. Both approaches now produce apps that feel fine.
Cross-platform, for most small businesses
The reason is not technical elegance. It is that one codebase means one set of changes, one bug fixed once, and one developer able to hold the whole thing in their head.
For a business with an internal app used by twenty staff, that is decisive. The alternative is paying twice for every change forever, or shipping features to iOS and letting Android fall behind, which is how you end up with half your team on a worse tool.
It also matters for handover. Finding one person who can maintain a React Native app is easier and cheaper than finding two specialists, and small businesses change suppliers.
When native genuinely wins
Not often, but the cases are real:
- Heavy sustained hardware use. Continuous video processing, augmented reality, custom camera pipelines, tight Bluetooth work with specific devices.
- The app is the product and its performance is the differentiator. If you are a software company competing on feel, build native.
- You need a brand-new platform feature on day one. Cross-platform frameworks lag OS releases by weeks or months.
- You already employ native developers. The best technology is frequently the one your people already know, and this is a perfectly respectable reason.
If none of those apply, and for most trades, clinics, charities and service businesses none do, cross-platform is the pragmatic answer.
The thing that actually determines the cost
It is not the framework. It is how much of the app needs to work offline.
An app that reads and writes to a server whenever you tap is straightforward on any technology. An app that has to hold a day’s work on the device, let someone edit it in a basement with no signal, and reconcile it later when two people changed the same record is a genuinely hard piece of software regardless of what it is written in.
Offline sync is where mobile projects overrun. If your requirement includes it, scope that specifically and early, rather than treating it as a checkbox. And if it does not, say so plainly, because a lot of apps get built offline-capable for a scenario that never happens.
What does not matter
App size. Nobody has abandoned an install over a few extra megabytes.
Framework popularity arguments. Both major cross-platform options are backed by large companies and used at scale. Either is a defensible choice in 2026.
Startup time, at the margins. The difference between the approaches is measured in fractions of a second and swamped by whatever your app does on launch.
The question to actually ask a developer
Not “native or cross-platform.” Ask: what happens when this needs a change in two years, and who will do it?
That question exposes the real cost. A native pair maintained by one contractor who left is a much worse position than a single cross-platform codebase any competent mobile developer can pick up. Ongoing ownership is the expensive part of an app, as what it costs to keep an app in the stores sets out.
And before any of this
Confirm you need an app. This entire decision is downstream of a question that is answered “no” more often than people expect, and the four tests take five minutes to apply.
If you have a use case and want a straight recommendation, describe what the app has to do and where it will be used. Whether people will have signal is usually the answer.
Related: does your business need an app, web app or website, and our mobile app work.
Further reading
Topics in this article
Get new articles by email
One email when something new goes up, roughly twice a month. Plain writing on what software costs and what is worth building. No sequences, no sales calls, and one click to leave.
Keep reading on the same subject
-
What it costs to keep an app in the stores
The recurring costs of owning a mobile app: developer accounts, forced platform updates, review cycles, and why apps rot faster than websites.
Budget for year two -
Does your business actually need a mobile app?
Four reasons an app genuinely beats a website, the reasons that are not real, and what an app costs to keep in the stores once it exists.
Apply the four tests -
Booking systems: when to buy one and when to build
Off-the-shelf booking software fits most businesses. The specific cases where it does not, and what building instead actually costs.
Weigh booking options