Do I Need an App, or Just a Better Website?

When someone tells me they need an app, they're usually describing one of three quite different things. Sorting out which one is the most valuable half-hour in the whole project, because the three options differ in cost by roughly an order of magnitude — and picking the expensive one when the cheap one would have worked is the most costly mistake available to you.

The short answer

You need a website if your goal is for strangers to find you, trust you, and get in touch.

You need a web app — a site people log into to do something — if your goal is for customers or staff to book, order, track, submit or manage something.

You need a mobile app — the kind installed from the App Store — only if you need something a browser genuinely can't do: push notifications people must not miss, working offline, camera or GPS as a core function, or customers who will open it several times a week for years.

Most businesses that ask me for a mobile app need the middle one. It costs a fraction as much, ships far sooner, works on every device including desktop, and doesn't need anyone to install anything or approve a store listing.

The three things people mean by “app”

A website is pages you read. Home, services, about, contact. Nobody logs in. Its job is to be found in search, explain what you do, and make it easy to contact you. That's not a small job — for most small businesses it's the one that actually generates revenue.

A web app is a website you log into and use. Your customers book a slot, place an order, upload a document, check the status of their job. Your staff see today's schedule, mark things complete, manage records. It runs in a browser, so it works on a phone, a tablet and the front desk computer without three separate builds.

A mobile app is downloaded from the App Store or Play Store and lives on the home screen. It can do things a browser can't, but it's two builds — iOS and Android — it needs Apple's and Google's approval to publish, every update goes through review, and users have to be persuaded to install it, which is a much higher bar than clicking a link.

Five questions that decide whether you need an app or a website

• Does someone need to log in? No — website. Yes — at least a web app.
• Will people use it more than once a week, for a long time? Occasional use — booking a table, checking an order — belongs in a browser. Nobody installs an app they'll open three times a year. Daily use by committed users is the main thing that justifies installation.
• Does it need to work with no internet? This is one of the clearest cases for a native mobile app. Field staff in areas with no signal, delivery drivers, site inspections — if the thing must work offline and sync later, a browser is the wrong tool.
• Do you need notifications people will definitely see? A phone notification that arrives on a locked screen is meaningfully different from an email. If your business depends on someone responding within minutes, that's a real argument for a mobile app.
• Is the camera, GPS or a device sensor central to what it does? Not “nice to have” — central. Scanning, photographing evidence on site, live location tracking. Browsers can do simplified versions of some of this; a native app does all of it properly.

If you answered no to questions three, four and five, you don't need a mobile app. You need a good web app, and you'll have it sooner and for less.

What each option costs and how long it takes

Using my own fixed-price bands as a reference point:

• Starting price — website from $300, web app from $800, mobile app significantly more since it's two platforms
• Typical timeline — website 2–3 weeks, web app 6–10 weeks, mobile app longer, plus store review
• Works on — website and web app run on everything with a browser; a mobile app only runs on the platforms you build for
• Updates — website and web app updates are instant; a mobile app update waits for store review each time
• Users must install — no, for a website or web app; yes for a mobile app, which is a real barrier
• Ongoing costs — domain and hosting for a website; domain, hosting and a database for a web app; the same plus developer account fees each year for a mobile app

The row people underestimate is users must install. Getting someone to download an app is a genuine marketing problem on top of your existing marketing problem. A web link works on the first click, from a text message, a search result or a QR code on your counter.

The other row that surprises people is updates. A web app change is live the moment I deploy it. A mobile app fix waits for review before it reaches your users — which stops being an abstract inconvenience the first time you have a bug in production.

The strongest argument for starting with a web app

Even if you eventually need a mobile app, building the web version first is usually the right sequence — and it's rarely wasted work.

A mobile app needs a backend: the database, the accounts, the business rules, the admin screens. That backend is the majority of the engineering, and it's exactly what a web app is. Build the web app, get real users on it, learn what they actually do rather than what you assumed, and then — if the case for installation is still there — the mobile app plugs into a backend that already works and has already been corrected by real usage.

Doing it the other way round means committing to your assumptions at the most expensive possible moment.

When you genuinely do need a mobile app

I'm not arguing nobody needs one. Build one when:

• Your users are staff or committed customers who'll open it most days
• It must work offline and sync when signal returns
• Push notifications are core to the product, not a marketing extra
• The camera, GPS or sensors do the actual work
• You're building a consumer product where being on the home screen is the business model

If two or more of those describe you, a mobile app is the right call and the extra cost is justified.

The mistake that costs the most

The expensive version of this decision isn't picking the wrong option — it's picking the most expensive option first, before anyone has used anything.

A mobile app built on assumptions takes months and a large budget to reach the point where you find out which assumptions were wrong. A web app reaches that point in weeks, for a fraction of the money, and every correction is cheaper because it deploys instantly.

Whichever direction you're leaning, the first version should be the smallest thing that solves the single most important problem. Everything else is a phase two you can fund with what phase one earns you.

Frequently asked questions

A few things people ask before we start:

Can a web app work on a phone?

Yes — a well-built one is designed for phones first and looks and behaves like an app on a small screen. It can also be saved to the home screen with its own icon, opening full-screen without a browser bar. For most business use cases that's close enough to an app that users don't notice the difference.

Can I turn my website into an app later?

Partly. The backend — accounts, data, business rules — carries over almost entirely, which is the bulk of the work. The interface has to be rebuilt for each mobile platform. That's why building the web version first is rarely wasted money.

Which is cheaper to maintain?

Web, by a clear margin. One codebase instead of two, no annual developer account fees, no store review for updates, and no risk of an operating system update breaking your app for half your users.

How do I decide if I'm still unsure?

Describe what you want to happen, not what you want built. If you can say “a customer should be able to X, and my staff should see Y,” any competent developer can tell you which option fits — and a good one will tell you if the cheaper option is enough.

Where to start

Write down the one thing this needs to do, and who does it. That single sentence is usually enough to settle the app-versus-website question in a few minutes.

If you'd like a straight answer on which one your situation calls for, book a free 30-minute call. I'll tell you if a website is enough, and I'll tell you if you don't need to build anything at all — that answer has saved more than one person a five-figure mistake.