App choices · 21 Nov 2026 · 5 min read
Progressive web app: what it is and when it fits
A progressive web app is a website that can behave like an installed app. It suits some businesses very well and others not at all.
The short answer
A progressive web app, or PWA, is a website built with a web app manifest and usually a service worker so it can be installed to a home screen, open in its own window and work in a limited way offline. It suits content, booking and simple tools. It fits less well when you need deep device features or store presence.
What a progressive web app is
A progressive web app is a website with extra abilities. Instead of a separate program downloaded from a store, it runs in the browser, and the browser can offer to install it to the home screen or desktop. Once installed, it can open in its own window without the usual browser bars, and with its own icon and name.
Two technical pieces make this work. The first is a web app manifest, a small file that gives the browser the name, icon and colours. The second is a service worker, a script that sits between the app and the network and can store files for later use. MDN's documentation describes the manifest as what lets a browser install the app, and the service worker as optional but common, mainly for offline use. Browsers also expect the site to be served over HTTPS, though the exact install criteria differ by browser and change, so check the current documentation.
The word "progressive" means the site works for everyone in a basic way and gains extra features where the browser supports them.
What a PWA can do
- Be installed from the browser, with an icon on the home screen or desktop.
- Open full-screen or in its own window.
- Load quickly on repeat visits by keeping files stored on the device.
- Show a custom offline page, or let people read or queue content when the connection drops.
- Send push notifications on platforms and browsers that support them, subject to the person's permission.
- Reach people through a link, with no store account and no download from a store.
- Update itself the next time it is opened, without waiting for store review.
It also keeps one codebase for every device, which tends to reduce the amount to build and maintain. If you already have a website, the step to a PWA may be small. Ask your developer what your current site would need.
What a PWA cannot do, or does less well
The limits depend on the browser and operating system, and they change. Platform makers add and adjust web features over time, so check the current documentation for the browsers your customers use. As a general guide, a PWA is weaker in these areas.
- Deep device access: some sensors, Bluetooth features, background tasks and system integrations are limited or missing in the browser.
- Store presence: a PWA does not appear in store search by default, so people will not find it by browsing the store.
- Install experience: installing from the browser is less obvious than tapping Get in a store, and people often need a prompt to understand it.
- Push and background behaviour: support varies between platforms, and browsers do not allow silent push.
- Performance for heavy graphics: games and complex animation are usually better as native apps.
- Payments through the store: you cannot use the store's in-app purchase system from a PWA.
None of these is a reason to rule out a PWA. They are a reason to list what your idea truly needs before choosing.
When a PWA is enough
A PWA often fits when the main value is information, a form or a simple tool, and when reaching people quickly matters more than store visibility. Typical examples are:
- A booking or ordering tool for a local business.
- A content or catalogue site that benefits from fast repeat loads.
- An internal tool for staff, shared by link.
- A way to test an idea before investing in native apps.
- A companion to a website, where an installed icon adds convenience.
It is also a sensible first step when budget is tight, because one build serves every device. If the idea succeeds, you can move to a store app later, using what you learned. We compare the options in native app versus web app: what to build first.
When you should build a store app instead
Choose a store app when the product depends on something a browser cannot give you: reliable background location, rich camera or sensor use, close links with other apps, or smooth high-end graphics. A store app is also the better route when you want people to find you by browsing the store, or when you plan to sell digital goods through the store's purchase system.
Some teams build native apps for each platform, others use a cross-platform toolkit, and the choice affects cost and speed. Each route has trade-offs in speed, cost and device access. The mobile app development service page lists what we build for stores.
How a PWA differs from a store app
| Question | Progressive web app | Store app |
|---|---|---|
| How do people get it? | Through a link, then install from the browser | Through the store listing |
| Review before release? | No store review | Store review for each version |
| Updates | Loaded when the app is opened | Downloaded as store updates |
| Device features | Limited by the browser | Broad access with permission |
| Codebase | One for all devices | One or several, depending on the approach |
| Found by store search? | Not by default | Yes, if the listing is well written |
The absence of store review is an advantage for speed, but it also means you carry responsibility for privacy and safety yourself.
Making a PWA feel like an app
Installability is a technical badge, not a design. People judge a PWA by how it feels, so plan the basics: large tap targets, layouts that fit small screens, a clear way back from every screen, and quick feedback when something loads. Decide what happens with no connection, and write a calm message for it. Test on real devices and in more than one browser, since behaviour differs. A reusable set of components helps keep many screens consistent, as our guide on design systems explains.
Planning points that still apply
A PWA is not exempt from the usual duties. If people create accounts, think through what happens when they ask to delete them, as we describe in account deletion and user data in apps. If you collect usage data, apply the same discipline as for any app and read app analytics privacy. Consent rules for cookies and tracking differ by country, so ask a qualified adviser.
Finally, ask for estimates on the same brief for each route, a PWA and a store app, so you see the real difference. Our guide on why app development quotes differ explains how to read them.
Related guides
- Mobile app development
- Native app vs web app what should you build first
- Account deletion and user data in apps what founders should plan
- App Development Estimates: What Makes Quotes Differ
Questions and answers
What can a PWA do and not do?
A PWA can be installed from the browser, open in its own window, load quickly, show an offline page and, where supported, send push notifications. It is weaker on deep device access, store search visibility and store-based purchases. Support varies by browser, so check the current documentation.
When is a PWA enough?
A PWA often suits booking tools, content sites, staff tools and early tests of an idea, where reaching people quickly matters more than store visibility. It is a sensible first step when budget is tight and one build must serve every device.
How does a PWA differ from a store app?
A PWA is reached through a link and installed from the browser, with no store review and one codebase for every device. A store app is found through the listing, reviewed for each version and can use more of the device. Each has trade-offs.
Does a PWA work offline?
It can, if the developer adds a service worker that stores files or content for later use. How much works offline depends on how it is built, so decide in advance which screens must work without a connection.
Can I turn my existing website into a PWA?
Often yes. The site needs HTTPS, a web app manifest and usually a service worker, plus a design that works well on small screens. Ask your developer what your current site would need before you plan the work.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.