A progressive web app, or PWA, is a website built to behave like an installed app. Visitors can add it to their home screen, it opens full screen without the browser bar, it loads quickly, it can work without a connection and it can send notifications. It is built with standard web technology and runs on any device with a modern browser.
This guide explains what PWAs can and cannot do, and when one is the right choice.
How a PWA works
Three things turn a website into a PWA:
- A web app manifest: a small file with the app's name, icons and colors, so it can be installed.
- A service worker: a script that runs in the background, caching files and data so the app loads fast and works offline, and receiving push notifications.
- HTTPS: required for these features.
Add a responsive design that works well on phones, and you have an app-like experience from a website.
What PWAs can do
- Install on the home screen with an icon.
- Open full screen like an app.
- Work offline for planned content and actions, then sync.
- Send push notifications, on Android and on recent iOS versions for home screen apps.
- Use the camera, location and file uploads through the browser.
- Update instantly for everyone when you deploy, with no store review.
Their limits
- Deep device features: Bluetooth, background tasks, advanced camera control and some sensors are limited, especially on iPhone.
- iPhone differences: installing takes a few manual steps, and some features arrive later or work differently than on Android.
- App store presence: people searching the App Store will not find a PWA there.
- Heavy performance: demanding games and graphics are better as native apps.
Where PWAs beat store apps
- Speed to launch: no store review, no separate builds.
- Cost: one codebase for all devices, including desktop.
- Updates: everyone gets the new version immediately.
- Reach: anyone with a link can use it, no download needed.
- No store fees on payments made through your own checkout.
Good uses for a PWA
- Internal tools: field service checklists, inspections, stock counts and approvals. See workflow approvals.
- Customer portals: account status, bookings, documents and messages. See how to build a customer portal.
- Ordering and booking: restaurants, salons, services and events.
- Content apps: news, guides, catalogs and menus that should work offline.
- A first version of an app idea, before investing in store apps.
Designing for offline
Offline support must be planned. Decide what should work without a connection: viewing recent data, filling in forms, taking photos. Store that data on the device and sync it when the connection returns, with a clear way to handle conflicts. Show users whether they are online and whether their changes have been saved. Field teams working in basements, rural sites or warehouses benefit most.
Notifications
Push notifications work in PWAs on Android and desktop, and on iPhone for web apps added to the home screen on recent iOS versions. Ask permission at a sensible moment, after the user sees the value, not on the first visit. Keep notifications useful and infrequent.
Speed matters even more
A PWA should feel as fast as an app. Cache the app shell, keep scripts small, optimize images and load data efficiently. The same techniques as for websites apply. See how to improve website speed.
Security and sign-in
PWAs use the same security as websites: HTTPS, secure sessions and server-side checks. Data stored on the device for offline use should be limited to what is needed, and cleared on sign-out. Modern sign-in methods, such as passkeys, work well in PWAs. See user authentication.
PWA vs native vs cross-platform
A PWA is usually the cheapest and fastest option. A cross-platform app, such as React Native, costs more but gives store presence and deeper device access. Native apps cost most and give the most control. Many businesses start with a PWA and add store apps when the need is proven. See React Native vs native apps.
Turning an existing site into a PWA
If your web application already works well on phones, adding a manifest, a service worker and offline handling can turn it into a PWA with modest effort. If the site is not mobile-friendly yet, fix that first; installability does not help a site that is hard to use on a small screen.
What it costs
Adding PWA features to a good mobile web app is often a small project. Building a new PWA costs about the same as a comparable web application, plus work for offline support and notifications. It is usually well below the cost of native apps for both platforms. See pricing and estimates.
Payments in a PWA
Because a PWA is a website, it takes payments through your normal checkout, such as a payment provider's hosted page or embedded form. Modern browsers support saved cards and wallet payments, which make checkout quick on phones. There is no app store commission on these payments, which can matter for subscription businesses and marketplaces. See payment integration.
Helping people install it
Many users do not know a website can be installed. On Android, browsers can show an install prompt, and your site can offer its own install button at a good moment. On iPhone, users add the app through the share menu, so a short illustrated hint helps. Only suggest installing to people who come back regularly; a first-time visitor rarely wants to install anything.
Measuring success
Track how many visitors install the app, how often installed users return, how many actions happen offline and how notifications affect return visits. Compare installed users with regular web visitors. These numbers show whether the app-like features are worth extending, or whether a store app is the next step.
Common mistakes
- Adding install prompts to a site that is hard to use on phones.
- Promising offline support without planning how data syncs.
- Asking for notification permission on the first visit.
- Assuming every feature works the same on iPhone and Android.
How to decide
- List the features you need, especially device features.
- Check each works in browsers on your users' devices.
- Decide whether app store presence matters for your users.
- If the features work and stores are not essential, start with a PWA.
- Plan a path to store apps if demand grows.
In short
A PWA gives you most of what an app offers at a fraction of the cost and with instant updates. It is a strong choice for internal tools, portals, ordering and first versions. Choose store apps when deep device features or store presence are essential.
If you are unsure, build the core of the app as a PWA first and watch how people use it. Real usage tells you far more about whether store apps are worth the investment than any upfront debate.