When a business needs an app instead of a website
· 1 min read · #mobile #product
Clients often arrive having already decided they need an app. Sometimes they're right. Often what they need is a website that works well on a phone, which costs a fraction as much and ships months earlier.
The questions that decide it
I ask four things:
- Does it need the device? Camera, offline storage, background location, push at the right moment. Real hardware needs are the strongest argument for native.
- How often does someone open it? Daily habits live on a home screen. Twice-a-year interactions live on a link.
- Who installs it? Every install is friction. If the audience is anonymous visitors, an app loses most of them before the first screen.
- Is there a second surface? Staff-facing tools, admin, scheduling — these are often better on the web even when the customer side is an app.
If none of the answers point to native, a well-built responsive web app is the honest recommendation, even though it's the smaller project.
The cost people underestimate
The build is not the expensive part. Two stores, two review processes, two release cadences, users stuck on a version from eight months ago, and a permanent obligation to keep up with OS releases — that's the real commitment.
An app isn't a deliverable, it's a subscription to maintenance.
The middle path
Plenty of products start as a web app used from a phone, prove the loop, and only then get a native client for the part that genuinely needs one — usually notifications and offline. Doing it in that order means the native app is built against a validated product rather than a guess.