Does your business actually need an app? An honest answer

Reviewed September 5, 2026. Practical studio guidance, with examples rather than measured client results.

We can build mobile apps, but the starting question is what the customer or team needs to do. An app should solve a requirement that justifies another product to build and maintain.

The question behind the question

An app request may be about repeat ordering, offline access, notifications or simply being easy to reach on a phone. Write down the requirement before choosing the delivery format.

Some of these needs can be met by a responsive website or web app. Device support and permissions vary, so test the required capabilities on the actual platforms your audience uses.

The test

An app earns its keep when at least one of these is true:

• People use it repeatedly. Weekly or more. A loyalty programme at a coffee shop, a gym schedule, an ordering app for regulars.
• It needs the phone itself. Camera, GPS in the background, bluetooth, offline use in a basement with no signal.
• Notifications are the product. Not marketing pushes, but genuinely useful alerts people would miss otherwise.
• It is for staff, not customers. Internal tools are where apps quietly pay for themselves.

If none of those are true, an app is a website with an install barrier in front of it.

And that barrier is real. Getting somebody to install an app is one of the hardest things in this business. They have to want it before they have experienced it, which is the wrong order.

What a modern website already does

Owners are often surprised how much of the app wish list is standard on the web now.

• Installs to the home screen with your icon, opens without browser chrome
• Sends push notifications
• Works offline for the pages already visited
• Uses the camera for uploads and scanning
• Takes payments, including Apple Pay and Google Pay
• Knows the visitor's location, with permission

A web app can avoid app store distribution and share a codebase across devices. Native apps can provide capabilities or a user experience that justify their additional work. Compare the actual requirements.

When we do say yes

Plenty of times, and the pattern is consistent. It is usually a business where the app is the operation rather than the marketing: a trades company whose crews need job details and photo upload in places with no signal, a clinic with a genuine appointment and records relationship, a shop whose regulars order the same thing every week and would genuinely use a one tap reorder.

In those cases the app is not a channel. It is the tool the business runs on, and it is worth building properly.

The order that saves money

If you are unsure, this is a useful sequence:

1. Build the web version first and make it installable.
2. Watch what people actually do with it for a few months.
3. If usage shows a genuine repeat pattern that the web cannot serve, build the app then, informed by real behaviour.

Use what you learn to decide whether to improve the website or build an app. Define what success would look like before committing the next budget.