“Should this be an app or a website?” is rarely the best first question. A better decision starts with the audience, the tasks they repeat, the capabilities those tasks require and the cost of operating each distribution channel over time.
The three realistic paths
| Approach | Strongest when | Main tradeoff |
|---|---|---|
| Responsive web | Reach, search discovery, sharing and fast publishing matter most. | Some deep platform capabilities and store-driven retention patterns are less direct. |
| Progressive web app | A web product also benefits from installation, offline behaviour or an app-like shell. | Capabilities and installation behaviour still vary by browser and operating system. |
| Native or cross-platform app | Frequent use, offline workflows, device integration or highly tuned interaction justify a dedicated product. | Distribution, review, release and maintenance become additional product systems. |
A practical decision sequence
- Define the job: list the few user tasks the product must make meaningfully better.
- Test capability requirements: distinguish a real dependency on device APIs or offline execution from a preference for app-like presentation.
- Model acquisition: compare links, search and instant access with store discovery, paid acquisition and installed retention.
- Model total ownership: include release governance, analytics, support, platform changes and duplicated design work—not only the first build.
- Choose the smallest durable system: a complementary app can be added later; maintaining unnecessary parallel products is harder to reverse.
Use evidence rather than labels
A web product can be fast, installable and usable offline. An app can still be the right answer when background work, hardware access or repeated high-value workflows are central. The label does not decide the experience; implementation quality and product fit do.
MDN’s current PWA overview explains how installable web applications combine normal URL-based access with selected app-like capabilities. Its best-practices guide also stresses cross-browser testing, deep links, accessibility and progressive enhancement.
Cornerstone and related archive
- Mobile Web vs. Native Apps. Revisited — the flagship historical argument behind this hub.
- iPhone app, mobile web and widgets — an earlier comparison of delivery models.
- Mobile web and iPhone apps, hand in hand — a preserved hybrid example.
- Mobile Web — the wider delivery and standards context.