Almost every request we get for a mobile app should not be a mobile app. That is not a sales position — an app is the more expensive build, so it would pay us better to agree with you. It is just usually the wrong tool.
Here is how to tell the difference before you commit the budget.
The one question that decides it
Does your product need something only the phone itself can do?
That means the camera in a real workflow, GPS running in the background, offline use, push notifications people would genuinely miss, Bluetooth, biometrics, or an integration with the device's own calendar or contacts.
If yes, you need an app. If no, you almost certainly need a mobile website — because everything else an app does, a well-built site does too, and without the parts that make apps expensive.
What makes an app cost more
It is not the design. It is everything around it.
- Two platforms. iOS and Android, tested separately, even from one codebase.
- App store review. Every release waits for approval, and approval can be refused.
- Versioning. Users run old versions for months. You support all of them.
- Distribution. Nobody installs an app for a business they have used once.
That last one kills more app projects than any technical problem. Getting somebody to install something is a far bigger ask than getting them to open a link, and if the answer to "why would they install this?" is "so they can book with us", the honest answer is that they will not.
An app makes sense when people use you weekly and would notice if it disappeared.
A site makes sense when people need you occasionally and need you to be one tap away.
What a good mobile website already does
People assume apps are the only route to a real product experience. They are not:
- Works offline, if built for it
- Installs to the home screen with an icon, no store required
- Sends notifications on Android, and on iOS once added to the home screen
- Loads instantly for a returning visitor
- Updates the moment you deploy — no review, no old versions
For most booking, ordering, enquiry and account-management jobs, that is the whole requirement.
When we do say build the app
- Field teams working somewhere with no signal
- Anything where the camera is the product, not a convenience
- Drivers, delivery, or logistics needing background location
- A tool used daily by staff, where a home-screen icon changes how the day runs
Those are real, and we build them — see mobile apps for how that works.
The cheapest way to find out
Build the mobile web version first. Watch how people actually use it for a month. If the usage is daily and the friction is real, you now have evidence for an app, and a working product to model it on. If usage is occasional, you saved yourself the app budget and you already have the thing your customers wanted.
That is not us avoiding the bigger project. It is the order that costs you least to be wrong in.