The Question To Settle Before Spending Anything
What do you need that a website cannot do?
Answer this honestly and a good proportion of app projects stop here, having saved a great deal of money.
Native apps mean two codebases, iOS and Android, alongside whatever you already have on the web. Three sets of changes for every feature, two app store review processes, two sets of maintenance, permanently. That is not a reason to avoid them. It is a reason to be certain.
For most business software, a web application that works properly on a phone delivers the same outcome at a fraction of the cost.
When Native Is Genuinely The Answer
Hardware you cannot reach from a browser. Sustained background location, Bluetooth devices, advanced camera control.
Working offline for real. Not a cached page: hours of use with no signal and reliable sync afterwards. Genuinely hard, and genuinely a native strength.
Notifications you depend on, particularly on iOS where web notification support arrived late and remains weaker.
Store discovery matters commercially. If people find products by browsing the store, absence is a real cost. For business software, where users are directed to it, it usually is not.
Performance beyond what a browser gives you. Graphics, heavy processing, sustained real-time work.
The Middle Option Most People Miss
A progressive web app: your web application, installable to the home screen, running without a browser bar, working offline, receiving notifications.
One codebase. No store review, no revenue share, updates live immediately rather than waiting for approval and adoption.
The honest limitations: installation on iOS is obscure, there is no prompt and users have to be told; some capabilities remain restricted; and there is no store presence.
For a lot of business software that trade is clearly worth making, and it is worth evaluating before committing to two native builds.
What Moves The Price
One platform or two. React Native shares most of the code and does not make it free; platform differences remain.
Offline requirements. The single biggest multiplier. Sync with conflict resolution is a substantial piece of engineering.
Hardware integration. Each device or sensor is its own body of work.
Store compliance. Review, privacy declarations, age ratings and the rejection cycles they produce.
Backend. An app is a front end. If it needs an API that does not exist yet, that is a separate build.
Where App Projects Go Wrong
Building an app because competitors have one. With no answer to what it does that the site does not.
Underestimating maintenance. Both platforms release annually and break things. An unmaintained app stops working, visibly, in public.
Ignoring the store timeline. Review can take days and rejections happen. An urgent fix is not immediate.
Forgetting installation is a barrier. Getting somebody to install and keep an app is a much larger ask than getting them to open a link.
Questions To Ask Whoever Quotes For This
- What does this do that a web app could not? Then check the answer against the PWA capabilities.
- What is the annual maintenance cost? Both platforms, indefinitely.
- Who owns the developer accounts? Should be your business, not the agency.
- How does offline work, precisely? Vague answers here become expensive later.
- What happens when Apple or Google changes something?
A Brief You Can Send Anyone
Who uses it: [staff, customers, or both]
Where they are when they use it: [office, on site, in a vehicle, no signal]
What they do in it: [the two or three core tasks]
Whether it needs hardware: [camera, GPS, Bluetooth, scanner]
Offline requirement: [none, brief, or hours]
Do they need to find us in the store: [yes / no]
What exists already: [website, web app, API]
How many users: [realistically, in year one]
How We Advise On This
We will tell you if you do not need an app, because the alternative is you paying for two codebases to deliver what one would have.
Where a web application will do, web application development plus proper mobile support is the cheaper and more maintainable route. Where native is genuinely required, React Native shares most of the work across both platforms.
Get in touch with what your users are doing when they reach for their phone.