"We should probably have an app." It's one of the most common things I hear from business owners, and it's almost always followed by the same uncertainty: an app for what, exactly?
An app sounds modern. It sounds like an upgrade. But a native mobile app is one of the most expensive things a small business can commit to building and maintaining — and most of the time, the thing the owner actually wants is a website that works better than the one they have. Here's how to tell the difference before you spend a dime.
Start With the Verb, Not the Noun
Don't start with "do I need an app." Start with what you want a customer to do:
- Book, browse, buy, read, or contact? That's a website. Full stop. These are the things the web does best, and forcing them into an app just adds a download step between your customer and the thing they came to do.
- Check something repeatedly, track progress, or use a tool day after day? Now an app might make sense, because you're asking someone to come back constantly — and an icon on their home screen is worth something.
The web has a built-in disadvantage and a built-in advantage. The disadvantage: you have to be found. The advantage: there's nothing to install. For most businesses, "nothing to install" wins, because the hardest part isn't getting someone to use your site — it's getting them there in the first place. Adding "go to the App Store, search, download, create an account" in front of that is friction most customers won't push through.
When a Website Is the Right Answer
For the overwhelming majority of local businesses, a modern website does everything an app would — without the cost, the download, or the app-store gatekeeping:
- Restaurants and shops — menus, hours, ordering, reservations
- Service businesses — quotes, booking, portfolios, contact
- Professionals — credentials, case studies, scheduling
- Retail and resale — a storefront customers can browse and buy from
If that's you, the move isn't to build an app. It's to build a website that loads fast, ranks in search, works flawlessly on a phone, and is built to convert visitors into customers. A well-built site does more for your bottom line than an app no one downloads.
When an App Actually Earns Its Place
There are real reasons to build a native app. If your idea genuinely needs one of these, an app stops being a vanity project and becomes the right tool:
- It works offline. No signal, no problem — the app keeps functioning and syncs later.
- It uses the device. Camera, GPS, Bluetooth, the secure wallet, background location — things a browser can't fully reach.
- It needs push notifications. Real, reliable notifications that bring people back, not email blasts they ignore.
- It's a daily habit. A tool people open every day earns a spot on the home screen. A brochure does not.
Notice these are about capability and frequency, not appearance. If your reason for wanting an app is "it'll look more professional," that's a design problem, and it's far cheaper to solve on the web.
The Middle Path Most People Don't Know About
There's a third option that lives between a website and a native app: a progressive web app (PWA). It's a website, built with web technology and found through a normal link — but it can be installed to the home screen, work offline, and send push notifications on most devices.
For a lot of businesses that think they're stuck choosing between a cheap website and an expensive app, a PWA is the honest answer: most of what makes an app feel like an app, without a separate iOS and Android build, without the app-store review process, and at a fraction of the cost to maintain.
The Cost Nobody Mentions: Maintenance
The build is the part everyone budgets for. The part that surprises people is what comes after.
A native app isn't a one-time purchase. iOS and Android ship updates every year that can break things. App-store policies change. You're often maintaining two codebases instead of one. And every update has to go back through review before your customers see it. A website, by contrast, you can fix and redeploy in minutes, and there's no gatekeeper between you and your audience.
That ongoing cost is exactly why I push back when someone asks for an app they don't need. It's not just more expensive to build — it's more expensive forever.
How to Decide in Five Questions
Run your idea through these. The more "yes" answers, the more an app makes sense:
- Will customers use it repeatedly — daily or weekly, not once?
- Does it need to work offline?
- Does it need device hardware (camera, GPS, Bluetooth)?
- Are push notifications central to how it works?
- Is the experience too involved for a browser tab to handle well?
Mostly "no"? You need a better website, and you'll get more business for less money. A few strong "yes" answers — especially around daily use and offline — and it's worth talking about an app, or a PWA as the middle ground.
The Honest Recommendation
I build both. Native apps and web applications are both things I design and ship end to end — so I have no incentive to steer you toward one or the other. That's exactly why my default advice is to start with the website. It's faster to launch, cheaper to run, easier to find, and for most businesses it does the entire job.
When an app is genuinely the right call, you'll know — because the reason will be a capability, not a feeling. And if you're not sure which camp you're in, that's a ten-minute conversation, not a guess.