18 April 2026 · 4 min read
Low usage frequency
Apps earn their install through repeated use. If a user needs your service twice a year, a fast website wins on every dimension including your cost.
Install friction is real and permanent. Every step between intent and use loses a share of users.
No device capability requirement
If you do not need the camera, background location, push at scale, or offline operation, the browser can do it. Progressive web apps cover more ground than most teams assume.
Push notifications alone are rarely worth the cost of two native codebases.
No team to maintain it
An app is a subscription, not a purchase. OS updates, store policy changes, and dependency deprecations mean ongoing work every year.
If there is no maintenance budget, the app will be broken within eighteen months. Better not to start.
Where to go from here
If you are weighing the app-versus-web decision for an upcoming project, the useful next step is usually a short scoping conversation rather than a longer article. Bring your constraints — budget, timeline, existing systems, and the team you already have — and the decision usually resolves itself in an hour.
We run these as a fixed-scope discovery session with a written recommendation at the end, including the cases where our advice is that you do not need us.
Working on something like this?
Send us the brief. We will tell you what we would build, what we would cut, and roughly what it costs.
Talk to us