Customers use phones for almost everything, so it is natural to conclude that your business needs an app. Sometimes it does. More often the need is for a website that works properly on a phone, which is a much smaller project, and the app would have sat unused on a few hundred home screens. The difference matters because apps are expensive to build and, less obviously, expensive to keep.
Start with the mobile-friendly website
A responsive website adapts to any screen, is found through search, opens from a link in a message or an email, and needs no installation. For the majority of businesses, that covers what customers want: find you, understand what you offer, contact you, book or buy.
If your current site is hard to use on a phone, fix that first. It costs less than an app, helps every visitor rather than the few who install something, and is what search engines rank.
When an app earns its place
An app makes sense when the way people use it is different from "look something up":
- Repeated, frequent use. Daily or weekly use by the same people: customers checking an account, staff logging work, members booking sessions.
- Device features. Camera for scanning or documenting, GPS for field work or deliveries, push notifications that people actually want, offline use where there is no signal.
- Logged-in workflows for staff or partners. Field engineers, drivers, inspectors, franchisees. An app on a work phone can be a better tool than a browser tab.
- A product that lives on the phone. If the app is the service, as with a fitness programme or a loyalty scheme, it needs to be an app.
If none of those apply, the honest answer is usually that an app would not be opened often enough to justify it.
The option in between: a progressive web app
A progressive web app (PWA) is a website built so that it can be installed on the home screen, loads fast, works partly offline and, on most platforms, can send push notifications. It is still a website: one codebase, no app store, updated instantly, found through search. For many "we need an app" requests, a PWA delivers most of the benefit at a fraction of the cost and without the store overhead.
Its limits are real: access to some device features is narrower than for native apps, and the install prompt is less visible than a store listing. For a customer-facing portal or a staff tool, those limits rarely matter.
If it has to be a real app
Two further choices follow.
- Cross-platform or native. Cross-platform frameworks produce iOS and Android apps from one codebase and suit most business apps. Fully native development, one codebase per platform, is justified for apps that push the hardware or need every platform-specific detail.
- Who maintains it. Apps need updating when operating systems change, when store rules change and when your business changes. There are also store developer accounts to keep, review processes to pass, and the back end that the app talks to, which is a web application in its own right. Budget for this as an ongoing cost, not a one-off build.
A sequence that avoids regret
- Mobile-friendly website. Non-negotiable; everything else builds on it.
- Progressive web app when customers or staff need an installable, fast, partly offline tool.
- Native or cross-platform app when the use case clearly needs device features, store presence or daily engagement that a PWA cannot deliver.
Each step reuses the one before. A business that follows this order rarely ends up paying for an app nobody opens.
Questions that settle it
- Who would use it, and how many times a week?
- What would they do in it that they cannot do on the website?
- Does it need the camera, location, offline mode or notifications?
- Who will keep it updated next year, and the year after?
If you can answer those, you can tell which option you need. If you would like help answering them, tell us how your customers or staff would use it and we will recommend the lightest option that does the job.