What a progressive web app is and who it is right for
A progressive web app is a website that installs, works offline and sends notifications, with no app store. What it can do, its limits, and who benefits most.
The short answer
A progressive web app, PWA, is a web application built so that it can behave like an installed app: added to the home screen with an icon, opened full screen without browser controls, able to keep working offline with what it has cached, and able to send notifications on the major platforms. It is still a website, built once, served from the web, updated the moment you publish. There is no store, no review and no separate codebase per platform.
For a large share of business needs, that is a real app in every way that matters to the person using it.
What it can do
| Ability | How |
|---|---|
| Install with an icon | From the browser, to the home screen, no store |
| Open full screen | No address bar or browser controls once installed |
| Work offline | Caches pages and data; queues actions until the connection returns |
| Notify | Push notifications on the major platforms, with the user’s permission |
| Use the camera, location, files | Through browser capabilities, on most devices |
| Update instantly | Publish once; every installed copy updates on next open |
| Serve every device | One codebase for phones, tablets and desktops |
Where the limits are
- Some hardware features are not reachable from the browser, such as certain sensors or deep system integration.
- Platform differences. Notifications, installation prompts and background behaviour differ between platforms, and iPhone has historically been more restrictive.
- Long offline sessions with large data are better served by native or hybrid apps built for that.
- Store discovery. If customers will search a store for you, a PWA alone is not there unless wrapped.
Who it is right for
- Client portals. Customers use it occasionally, install from a link if they like, and it is always current.
- Booking and ordering tools. Fast, installable, no store friction between a customer and a booking.
- Field forms and inspections. Staff install from a link; occasional gaps in coverage are covered by caching and queued submissions.
- Internal tools. Everyone gets an icon without IT distributing anything.
- Customer tools used often, where a home screen icon beats a bookmark and a store listing is not needed.
What this means for you
Before commissioning a mobile app, ask whether a progressive web app covers the job: install from a link, offline for what has been seen, notifications where supported, one codebase, instant updates. For a business tool the answer is yes, and it removes the stores, the yearly platform updates and the second codebase from the picture entirely.
Frequently asked questions
How does a user install it?
From the browser: a prompt or a menu option adds it to the home screen with an icon. It then opens full screen like any app. No store, no account, no download step beyond that. For staff, a link in an email is the whole rollout.
Does it work when there is no signal?
For what it has cached, yes: pages, data it has seen, and actions queued to send when the connection returns. For hours of heavy offline work with large local data, a native or hybrid app is the safer choice.
Can it be in the app stores too?
Yes, wrapped, if store presence matters for discovery. Many businesses do not need it; their users install from a link. The option exists without rebuilding.
Sources
- MDN Web Docs: Progressive web apps (accessed 2026-09-11)