A progressive web app, or PWA, is a website built so it can behave like an installed app. Visitors can add it to their home screen, it opens in its own window without browser bars, and it can still show content when the connection drops. There is no app store involved: the install happens from the browser.
The three pieces that make a site a PWA
- HTTPS. Browsers only enable PWA features on secure origins, so the site must be served over HTTPS.
- A web app manifest. A small JSON file listing the app's name, icons, theme colour, start page and display mode (for example
standalone, which hides the address bar). - A service worker. A script that sits between the page and the network. It can store files in a cache and serve them when offline, and it is what receives push messages.
What browsers actually support
Chrome and Edge on Android and desktop show an install prompt or menu option. On iPhone and iPad, users install through Safari's Share menu, "Add to Home Screen". Apple added web push notifications for home-screen web apps in iOS 16.4, so a PWA on iOS can now notify users, but only after it has been added to the home screen. Feature support still differs between browsers, so check before relying on anything beyond caching and installation.
An example: a café's order-ahead PWA
A café puts its menu and pre-order form on a PWA. Regulars add it to their home screen once. The service worker caches the menu, so it loads instantly on the café's patchy Wi-Fi, and the order form queues a submission until the connection returns. The café avoids app store fees and review delays, and every update goes live as soon as the site is redeployed.
Is a PWA worth it for your business?
If customers come back often from their phones, making your web app installable is a cheap upgrade. For a brochure site visited a few times a year, skip it: few people will install it. If you need deep hardware access or app store visibility, look at a native or hybrid app instead.
PWA pitfalls
- Caching too aggressively. A careless service worker keeps serving old prices or old code long after you change them. Version your caches.
- Missing icon sizes. Without proper manifest icons the install prompt may not appear or the home-screen icon looks blurry.
- Promising iPhone users an install button. iOS has no automatic prompt, so explain the Share menu step.
- No offline page. Give users a friendly screen instead of a browser error when nothing is cached.
Related terms
- Web app: what a PWA is underneath.
- Native app: the app store alternative.
- Caching: the idea behind a PWA's offline mode.
- HTTPS: required before any PWA feature works.