Do you actually need a mobile app, or will a website do?

We build mobile apps. So it is worth being upfront: most of the time, when somebody asks us for one, our honest recommendation is not to build it.

Not because apps are bad, and not because the work is uninteresting. It is because an app carries a cost profile most people are never shown before they commit, and because the thing they actually wanted — more customers — is something an app is unusually bad at delivering.

Here is how to tell which side of that line you are on.

Start with the download problem

This is the part that decides it for most businesses, and it has nothing to do with technology.

To use your website, someone taps a search result. To use your app, they have to find it in a store, decide it is worth space on their phone, wait for it to install, and usually create an account. That is a lot of steps, and each one loses people.

Crucially, they have to be willing to do all that before they have got any value from you. A stranger who has never heard of your business will not do it. They will use whichever competitor let them book, price or buy in the browser they already had open.

The four reasons an app is genuinely the right call

These are the cases where a website cannot do the job, no matter how well it is built. If none of them describes you, you are probably looking at a website.

1. It has to work without a connection

A field crew in a rural area, an inspector in a basement, a technician in an underground parkade. If the work happens where the signal does not reach, and data has to be captured then synced later, that is an app.

Websites can do a limited version of this, but "limited" is the operative word. If offline is a core requirement rather than a nice-to-have, build the app.

2. It has to do something while nobody is looking at it

Tracking a route in the background, monitoring a Bluetooth sensor, logging activity through the day. A website only runs while its tab is open and in front of the user. An app can keep working when the phone is in a pocket.

3. It needs deep access to the hardware

Ordinary camera access, basic location and file uploads all work fine on a website — that surprises people. What does not is the deeper end: continuous background location, Bluetooth accessories, NFC in most cases, advanced media processing, or tight integration with the phone platform itself.

4. Notifications are central to how it works

If the product does not function without reliably reaching the user — a dispatch tool, a two-way messaging service, a critical alerting system — an app gives you a far more dependable channel than the web does, particularly on iPhones.

Be honest about the word "central", though. Wanting to send occasional promotions is not this. Email and text already do that, and they reach people who have not installed anything.

The costs nobody mentions in the sales conversation

The build price is the part everyone discusses. It is rarely the part that causes regret.

That fourth row is the one that catches people. An app is not a thing you buy once. It is a thing you keep, like a vehicle — and if you stop maintaining it, it does not sit there working. It degrades and eventually disappears from the store.

The middle option most people have not been told about

There is a third answer between "website" and "app", and it fits a surprising number of the businesses that come to us asking for an app.

A modern website can be built so that it installs to the home screen. It gets its own icon, opens without browser chrome around it, works offline to a degree, and on Android can send notifications. To the customer it looks and feels much like an app. There is no store, no review queue, no download, and it is one thing to maintain rather than three.

The trade-offs are real and you should know them: notification support on iPhones is weaker and has more conditions attached, deep hardware access is limited, and you do not get a listing in the app stores — which matters if store presence is itself part of what you are buying.

But if what you wanted was "our regulars can tap an icon and book in two seconds", this often delivers it for a fraction of the cost and none of the ongoing store obligation.

What we usually recommend instead, and why

When a small business tells us they want an app, the underlying goal is almost always one of three things. None of them needs an app.

• "We want more customers." An app cannot do this — people do not download apps for businesses they have not heard of. Being findable on Google and having a site that answers the price question does it.
• "We want to look professional." A well-built website does this more reliably than an app nobody has installed. An app with three downloads and a 2023 copyright notice does the opposite.
• "We want customers to book and pay easily." A good booking flow on a website does this now, for everyone, with no install step in the way.

Prince, a detailer in southeast Calgary, is a fair example. He came to us needing customers to find him and to stop quoting every job by phone. An app would have solved neither — his customers are strangers searching Google, and no stranger installs an app to get a price. What he needed was a website that shows up in search, a tool that prices a job without a phone call, and invoicing he can send from a phone. That is what we built.

One exception is worth naming. If what you are building is a product you intend to sell, rather than a tool for running a business you already have, the question changes shape. There the first step is usually a deliberately small version that tests whether anyone wants it — and the argument about which platform it lives on can wait until you know the answer to that.

A decision you can make in five minutes

Work down this list. Stop at the first "yes".

1. 1Does it have to work with no connection? → Build the app.
2. 2Does it have to run in the background, or use Bluetooth or continuous location? → Build the app.
3. 3Is reliable notification delivery the core of the product, not a marketing extra? → Probably the app.
4. 4Do the same people use you weekly or more, and would genuinely value a two-second route in? → Consider the installable website first, then the app if that falls short.
5. 5None of the above? → Build the website properly. Spend the difference on being findable.

One last thing worth saying, because it comes up constantly: choosing the website now does not close the door. A well-built site and a solid backend are the same foundation an app would need later. If the business grows into needing one, you will not be starting again — and you will know far more about what the app should actually do, because real customers will have told you.

Deciding later, with evidence, is almost always cheaper than deciding now, on a hunch.