The instinct to build an app usually arrives before the evidence for one does. An app sounds like the serious, grown-up version of a mobile presence, and a competitor having one makes the pressure worse. But an app is not a website with an icon — it is a second product, with its own build, its own update cycle and its own ongoing cost, and it only pays for itself in specific conditions that a genuinely honest audit can check for before any of that spending happens.
Start with what a mobile site cannot do
A responsive mobile site already covers most of what businesses assume they need an app for: fast loading, clean navigation, forms that work on a small screen, a checkout that does not require pinching and zooming. If the mobile site is slow, cluttered or broken on a phone, an app will not fix that — the same team, the same content decisions and often the same underlying problems will simply be rebuilt inside a second product. Fixing the site first is usually the honest first step, and it is almost always the cheaper one.
What an app actually earns its cost on
An app makes sense when the relationship is frequent and ongoing rather than occasional — a loyalty programme people open weekly, a booking flow customers return to, a service that benefits from push notifications, offline access or device features like the camera or location that a browser cannot use as smoothly. If the honest answer to "how often would someone realistically open this" is a handful of times a year, an app is solving a problem the business does not actually have.
The store gatekeeper is not free
Beyond the build cost, an app has to be discovered and downloaded before it does anything, and both app stores impose review processes and account requirements that add friction and time to every release. None of that is a reason to avoid an app outright, but it means the true cost of "having an app" includes an ongoing relationship with a platform the business does not control — a cost that a mobile site never carries.
A more honest ordering
The sequence that avoids wasted spend is: fix the mobile site first, measure how people actually use it, and only then evaluate whether an app would remove real friction that the site genuinely cannot. In many businesses that evaluation ends the conversation — the mobile site, done properly, was what people needed. In the cases where it does not, the decision to build one is made with evidence instead of assumption, which is the same discipline behind deciding how to acquire any piece of software rather than defaulting to the most impressive-sounding option. Our mobile team can run that audit honestly, including telling a client the app is not worth building yet — which is not the answer that pays best, but it is the one that is usually true.
