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.
Most small businesses that want an app do not need one, and the ones that do usually need it for a reason nobody mentioned in the first meeting.
An app is not a website with an icon. It is a second product, in two stores, with review processes, forced updates and its own maintenance. Worth it when one of four things is true, and expensive when none of them are.
The four reasons that are real
1. It has to work without signal. Crews in the field, rural sites, basements, anywhere the connection drops. A web page needs the network at the moment you use it. An app can hold the day’s work locally and sync when it gets back. If your people work where the signal does not reach, this alone justifies an app.
2. Push notifications people actually act on. Not marketing. Operational messages: a job assigned, a shift changed, an alarm. Web push exists and is weaker, especially on iOS, and reliability is the whole point when the message is “the site flooded.”
3. It needs the hardware properly. Continuous camera work, barcode scanning all day, background location, Bluetooth to equipment. A browser can do a little of this and does it awkwardly.
4. It is used many times a day by the same people. An app opened forty times a day earns its icon. Something used twice a year does not, and will be deleted to free up space.
Notice that three of the four describe staff, not customers. That is not an accident, and it is the most common correction we make to an app brief.
The reasons that are not real
“Our competitors have one.” Check whether it has been updated in two years and what the reviews say. A neglected app is worse than no app, because it is public evidence of neglect.
“To be on people’s home screens.” Getting installed is the hard part. People install a handful of apps a month, and almost all of them are ones they already know they need.
“It will be a marketing channel.” Only if people install it, and they install it because it is useful, not to receive offers. The order matters.
“It’s more professional.” A slow, dated app is less professional than a fast website. Nobody has ever judged a plumber by their app.
“So customers can book.” A booking page on your website does this, works from a search result with no install step, and has none of the maintenance. Booking systems is a different and usually cheaper conversation.
Try the harder question
Not “would an app be useful?” Almost anything would be useful. Ask:
Will someone install this, and open it again next week?
That is a much higher bar and it kills most customer-facing app ideas outright, correctly. It is also why internal apps succeed more often: staff install what they are told to and use it because it is the tool for the job.
What it costs after it is built
The build is not the expensive part over time. Apps have running costs a website does not:
- Apple’s developer programme is an annual fee; Google’s is a one-off.
- Both platforms force you forward. Operating system releases every year, and periodic minimum-SDK deadlines that make an app stop being updatable if you ignore them. An app left alone for two years often needs real work before it can be submitted at all.
- Every change goes through review, so shipping a fix is not instant.
- Two platforms, even from one codebase, means two sets of store admin, screenshots, privacy declarations and release notes.
Budget for an app being a thing you maintain forever, not a thing you buy once. A site you can leave alone for a year; an app you cannot.
The middle option most people miss
A responsive website, installable to the home screen, works offline for reading, and needs no store at all. It covers a surprising amount of the ground between a plain site and a real app, with none of the store overhead.
It genuinely cannot do the hardware-heavy or reliable-notification cases, particularly on iOS. But if your requirement is “our page, on their phone, fast, with an icon,” start there and only build an app when you hit a wall you can name.
The honest starting point
Write down the single task the app exists to do, and who does it, and how often. If that sentence describes staff doing something daily in the field, build the app. If it describes customers doing something occasionally, build the website properly instead.
If you want a straight read on which side you are on, describe who would use it and how often. “You do not need an app for that” is an answer we give regularly.
Related: web app or website, what it costs to keep an app in the stores, 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
-
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.
Settle the choice -
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 -
Web app or website: which one do you actually need?
The difference between a website and a web app in practical terms, what each costs to build and run, and how to tell which one your business needs.
Tell the two apart