You probably don't need an app

A lot of businesses assume they need an app. Occasionally they’re right. Usually what they need is a website that works properly on phones, and the difference is tens of thousands of dollars, so it’s worth sorting out the vocabulary before anyone quotes you anything.

What “app” usually means

When people say “app,” they almost always mean: something my customers or staff open on their phone that does a job. Book a slot, check a schedule, submit a form, see their account. Here’s the thing: every one of those is a website. A modern web app looks and feels app-like, works on every phone without an app store, updates instantly for everyone, and needs one codebase instead of two.

An icon on the home screen? Web apps can do that too: visitors can install your site like an app, no store involved. For most small businesses that covers 100% of what “we need an app” meant.

What a native app costs

A real app-store app means building the thing at least twice (iOS and Android), then maintaining both forever, plus a cut of any in-app payments, plus review processes that can hold your bug fix hostage for days. Realistic small-business app projects start where serious custom software budgets start, and go up. It’s not a website with extra steps; it’s a second product.

That money is justified sometimes. Which brings us to the short list.

The few good reasons to build native

Your users have no signal. Field crews syncing job data from places with no coverage. Offline-first is where native earns its keep.

You live on the phone’s hardware. Heavy camera use, barcode scanning all day, background GPS tracking. Browsers can do more of this than people think, but at the intensive end, native wins.

Push notifications are the product. If the entire value is tapping people on the shoulder at the right moment, native still does this best (though the web has closed most of this gap too).

Your customers will open it weekly. An app that earns a permanent spot on someone’s home screen is rare. Be brutal with yourself here: people install apps for things they do constantly, not for businesses they visit twice a year.

No item on that list? Build the web version. It’s the same decision logic as custom vs. off-the-shelf: match the tool to the job, not to what feels impressive.

The usual right answer

For customer-facing needs, it’s a fast, well-built website: one that loads in under two seconds and works beautifully on a phone, which is where most of your visitors already are. For internal tools, it’s a web app your team opens in a browser tab or from a home-screen icon, no app store between you and your own software.

If someone’s quoted you an app and it didn’t come with the list above, run it past me. Telling you the web version does the same job for a fraction of the money is a short, satisfying conversation.