“We should have an app.”
I hear this a lot, and I understand why — an app feels like the modern, serious thing to have. But it’s one of the most expensive assumptions a small business can make, and most of the time the honest answer is: you don’t need one. Here’s how to think it through before you spend real money.
What people usually mean
When a small-business owner says “we need an app,” they almost never mean a native app in the App Store. They mean something more like:
- “Our website is painful to use on a phone.”
- “I want customers to be able to book / order / check something easily on their phone.”
- “I want to send people notifications.”
Every one of those has a solution. Often it isn’t a native app at all.
The three real options
A better mobile website. If the actual problem is that your site fights people on a phone, a mobile-first website fixes that at a fraction of the cost — and there’s nothing to download, nothing to get past app-store review, and nothing to maintain in two places.
A progressive web app (PWA). This is the option most people don’t know exists, and it’s usually the right one. A PWA installs to the home screen like an app, works offline, and can send notifications — but it’s one codebase, no app store, and far cheaper to build and maintain. For most businesses that think they want an app, this is the app they want.
An actual native app. Sometimes the real answer. But only in a fairly narrow set of cases.
When native is genuinely worth it
A native app earns its considerable cost when you need:
- Deep hardware integration — background location, Bluetooth peripherals, heavy camera use.
- Serious offline field work — technicians working for hours somewhere with no signal.
- App-store presence as a real distribution channel — where customers will genuinely discover you by searching the store.
If one of those describes you, native is worth the conversation. If none of them does — and for most small businesses, none of them does — a native app is a large bill for something a PWA or a good mobile site would do better.
The math nobody mentions
A native app isn’t a one-time purchase. It’s two codebases (iOS and Android), ongoing OS updates, app-store compliance, and someone to maintain all of it. A common and expensive outcome is an app that gets built, used briefly, and then quietly abandoned eighteen months later while still costing money.
That’s the part that makes “we should have an app” so expensive: the build is only the beginning.
How to decide
Before you spend anything on building, spend a little on deciding. Work out — honestly — what you actually need the thing to do, then match it to the cheapest option that does the job:
If the real need is “work well on a phone,” you need a better website. If it’s “app-like experience without the overhead,” you need a PWA. If it’s genuinely hardware, offline, or store distribution, you need native.
I’ve built native apps, which is exactly why I’ll talk you out of one when you don’t need it. The goal isn’t the most impressive technology — it’s the thing that solves your problem for the least money and the least maintenance. Most of the time, that isn’t an app.
← All writing