Does Your Business Really Need a Mobile App?

We get asked to build mobile apps fairly often. A good share of the time, our honest answer is that the business doesn't need one.

That is an odd thing for a company that builds mobile apps to say, so let me explain the reasoning — because when an app is right, it is genuinely transformative, and when it is wrong, it is one of the most expensive mistakes a small business can make.

The uncomfortable truth about app downloads

Getting someone to install an app is genuinely hard.

Think about your own phone. How many apps do you have? How many did you open this week? Most people cycle through a small handful daily and ignore the rest. Some were opened once and never again.

Now consider what you're asking a customer to do: leave what they were doing, go to an app store, search for you, wait for a download, find space on their phone, create an account, and remember you exist tomorrow.

Compare that with tapping a link and being on your website in two seconds.

That gap is the whole decision. An app asks for commitment up front and repays it with convenience later. If there is no "later" — if the person genuinely only needs you once or twice a year — you are asking for a commitment you cannot repay.

When a mobile website is the right answer

Choose a website (or a better mobile website) when:

• people interact with you occasionally rather than routinely;
• most of what you offer is information — services, prices, availability, contact;
• you need to be found by new customers through search;
• someone should be able to act the first time they hear about you, without installing anything;
• your budget is limited and must reach the most people;
• transactions are infrequent — an annual service, a one-off purchase, an enquiry.

A well-built mobile website reaches everyone with a browser, appears in Google, needs no approval from Apple or Google to update, and costs a fraction of an app to maintain. For most small businesses it is simply the better instrument.

Worth saying: a modern website can do more than people assume. It can work offline to a degree, be saved to a home screen, send notifications on Android, and use the camera and location. The gap between "good mobile website" and "app" is narrower than it was.

When an app genuinely makes sense

An app starts to justify itself when at least a couple of these are true:

• People use it frequently — daily or several times a week. Frequency is the single strongest signal.
• You need real device capabilities: reliable offline use, background location, Bluetooth, continuous camera scanning, biometric login.
• Notifications are core to the value, not just a marketing channel — a delivery status, a shift change, a critical alert.
• It's a tool for a known group: your staff, your drivers, your existing members, your franchisees. You're not fighting for downloads from strangers.
• The experience must be fast and fluid in a way a browser genuinely struggles with.
• There's an ongoing relationship — subscriptions, loyalty, accounts, memberships with regular touchpoints.

Notice how many of these describe internal or existing-customer apps rather than customer-acquisition apps. That's not an accident. Apps are usually poor at winning new customers and excellent at serving people who already chose you.

The decision table

Your situation	What you likely need
Restaurant wanting to show a menu and take bookings	Mobile website
Restaurant with a loyalty scheme customers use weekly	App worth considering
Service business wanting more enquiries	Mobile website
Field team logging jobs on-site, often without signal	App
Retailer selling online	Mobile-first store, app later at scale
Clinic taking appointments a few times a year per patient	Mobile website
Gym with daily class booking and check-in	App worth considering
B2B company with a long sales cycle	Website, plus perhaps a customer portal
"Our competitor has one"	Neither — work out why first

That last row is not a joke. It's one of the most common reasons given, and it's the weakest.

The cost nobody quotes you

The build price is the part everyone focuses on. It's rarely the part that hurts.

An app is a commitment that continues:

• Both platforms. iOS and Android, unless you deliberately pick one. Cross-platform tools like React Native and Flutter let one codebase serve both, which genuinely helps, but it's still two stores and two sets of rules.
• Store approval. Every update goes through review. Apple and Google can reject builds. You do not control your own release schedule the way you do with a website.
• Mandatory maintenance. This is the one that surprises people. Operating systems update annually. Apps that aren't maintained eventually break or get removed from the stores. An unmaintained website looks dated; an unmaintained app stops existing.
• Getting installs. Nobody stumbles onto your app the way they find your website through search. Downloads must be earned — usually through the website, email or in person.
• Support. More versions of your software in the wild, on more devices, in more states.

Budget for the app's second and third year, not just its first. If those numbers don't work, the answer is already clear.

A sensible sequence

For most businesses that think they want an app, this order costs less and teaches more:

1. Make the mobile website genuinely good

Not merely responsive. Fast, easy to use one-handed, with the important actions reachable in a tap or two. Many "we need an app" conversations end here, because the actual complaint was that the mobile site was painful.

2. Build the functionality on the web first

If you want bookings, accounts, ordering or tracking, build it as a web application. Everyone can reach it immediately, and you find out whether people actually use it.

3. Watch the behaviour

Are people coming back weekly? Are they asking for offline access or notifications? Are they using it enough that installing something would genuinely serve them?

4. Then build the app

Now you know what it should do, because people have been using the web version. You build the app people already want rather than the app you hoped they'd want.

This sequence has an obvious advantage: if step 3 says the frequency isn't there, you've saved the entire cost of an app — and still improved your business.

The question to ask yourself

Forget technology for a moment and answer this honestly:

What would a customer do with this more than once a week?

If you have a clear, specific answer that survives a sceptical follow-up question, an app may be right. If the answer is "well, they could check things" or "it would keep us front of mind", that's a website with good email marketing.

If you're weighing this against other investments, our guide to where to spend first — website, SEO or Google Ads may help sequence the decision, and what to automate first covers the same discipline applied to internal tools.

Apps are wonderful when the frequency is there. When it isn't, they're an expensive way to be ignored on someone's fourth home screen. The honest question isn't whether you could have one — it's whether anyone would open it twice.