An app, or a website
Almost every business that asks for an app needs a website that works properly on a phone.
The question is whether people will return often enough to justify an icon on their home screen. A few times a year means a website that works properly on a phone. Weekly use, offline, camera, sensors or reliable notifications means an app.
Is it a fit?
Return rate
People come back weekly, not a few times a year.
Device
You need offline, the camera, sensors or reliable notifications.
Editing
Somebody in house can change content without waiting for a release.
Start here. Six questions pressure test what you are building before it costs anything.
Pressure test itWork it out in a minute
Four numbers and one question about fit. Gives you the answer and what it is worth.
The six real options
A responsive website
One codebase, no install, indexed by search engines and readable by assistants.
A progressive web app
A website that installs to the home screen, works offline and can send notifications on most platforms.
A native app
Built for one platform, with full access to hardware and the best possible performance.
One codebase, both platforms
A single build shipped to iOS and Android.
Why most app projects were website projects
A large share of app projects were website projects that nobody re-examined after the first meeting. The request arrives fully formed, as an app, because that is the word people use for software on a phone, and the actual need underneath it is that the current site is unusable on one.
The install step is the thing that gets underestimated. Every install is a decision, and every decision loses most of the people in front of it. A website asks for nothing. An app asks for a store visit, a download, permissions and an account before anybody has seen a single thing of value.
Whichever wins, MVP development keeps the first version small enough to finish. Either way somebody has to draw the screens, and UI and UX design is that work.
Website or app
Eight factors, read across. The first and the last row decide most cases, and both are about being found rather than about what the software can do.
| Factor | Website | App |
|---|---|---|
| How people find it | A search, a link, a message. There is no install step. | A store search or a link you send. There is always an install step, and most people do not take it. |
| Best for | Discovery, occasional visits, anything you want people to share. | Frequent use, logged in use, work somebody does every week. |
| Update cycle | You ship and it is live. | You ship, a store reviews it, then users have to update. |
| Hardware access | Camera and location with permission. No deep integration. | Camera, sensors, background work, and notifications that arrive. |
| Offline use | Limited, and achievable with effort. | Native to the format, and often the entire reason the app exists. |
| Cost over time | One codebase, one deployment, one thing to maintain. | Two platforms and two review processes, permanently. |
| Notifications | Possible, weaker on some platforms, easy to ignore. | The strongest return channel there is, and the easiest one to abuse until it is switched off. |
| Being found at all | Search engines index it and assistants can read and cite it. | Store discovery is close to zero without an existing audience or paid installs. |
Nothing here is about capability. Both can do most of what a business needs. The question is the install step and whether the frequency of use ever pays it back.
Five questions before you build an app
These take one meeting. Teams that answer them either build something much smaller than planned or stop and fix the site instead.
- How often will one person open it in a month?Below about four, an icon on a home screen is not earned and the install step will lose you more people than the app gains.
- Does it need something only a phone can do?Background location, a sensor, offline work, reliable notifications, deep camera integration.
- Where do the first thousand users come from?Answer this before the build, not after it.
- What breaks if a store rejects an update?Store review sits between you and your users forever.
- Have you shipped the mobile web version first?It is faster to build, it tells you what people use.
Questions we get
We were told we need an app to look credible. Is that true?
Credibility comes from the thing working, not from the format. An app with forty downloads and no recent update reads worse than a fast, well built site.
What is a progressive web app, in plain terms?
A website that can be added to a home screen, opened like an app, work offline and send notifications on most platforms. No store, no install friction, one codebase.
Should we build for iOS or Android first?
Whichever your users are on, which is worth checking rather than assuming, since it varies enormously by market and by sector.
How long does an app take?
Longer than the estimate, because store review, device testing and account handling absorb time that rarely appears in the plan.
More in the guides and every answer in one place.
Your results so far
Kept in this browser, sent nowhere.
By Shaheer Shaikh, technology and operations consultant · Updated October 3, 2026
Read next
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built