A progressive web app (PWA) is a website that behaves like an app. People can install it to their home screen, open it full screen without browser bars, use it on patchy connections and, in many cases, receive notifications, all without visiting an app store. For the right product, a PWA delivers most of the benefit of a native app for a fraction of the cost. For others, it's the wrong tool. Here's how to tell.
How a PWA works
Three ingredients turn a website into a PWA:
- HTTPS: the site must be served securely.
- A web app manifest: a small file describing the app's name, icons, colours and how it should open.
- A service worker: a script that runs in the background, caching files so the app loads quickly and works offline, and handling push notifications.
Because it's still a website, a PWA is also findable in search engines and shareable with a simple link.
PWA vs native app vs website
| Website | PWA | Native app | |
|---|---|---|---|
| Install to home screen | No | Yes | Yes, via app store |
| Works offline | No | Yes, with caching | Yes |
| Push notifications | No | Yes (with some platform limits) | Yes |
| Found in search engines | Yes | Yes | No (app store search instead) |
| App store listing | No | Optional (Play Store; limited on Apple) | Yes |
| Device features (camera, GPS, Bluetooth) | Some | Some to many | Full access |
| Updates | Instant | Instant | Through store review |
| Codebase | One | One | Usually one per platform, or cross-platform |
| Relative cost | Lowest | Low to medium | Highest |
What PWAs do well
- Speed on repeat visits, because files are cached on the device
- Working on poor connections, such as on trains or in warehouses
- No app store friction: people install straight from your site
- Instant updates, with no waiting for review
- SEO: every screen can be a findable, linkable page
- One codebase for desktop, Android and iPhone
Where PWAs fall short
- Deep device access: advanced Bluetooth, background location and some sensors are limited, especially on iPhone.
- App store discovery: if your customers search the App Store for apps like yours, you'll want to be there.
- iPhone limitations: installation is less obvious to users, and some capabilities lag behind Android.
- Perception: some users still expect "a real app" for certain services.
When a PWA is the smart choice
- Internal tools for staff, such as field service, stock checks and timesheets
- Booking, ordering and loyalty experiences
- Content and media sites that want offline reading
- E-commerce stores wanting app-like speed without a separate app
- MVPs testing demand before investing in native apps
When to go native or cross-platform
- The app relies heavily on device hardware or background processing
- App store presence is central to how customers find you
- You need advanced features like widgets, deep OS integration or complex offline sync
- You're building a consumer app that competes in crowded app store categories
Our guide to native vs cross-platform development covers that decision in depth.
PWA checklist
- Served over HTTPS
- Web app manifest with name, icons (including maskable icons) and theme colour
- Service worker caching the app shell and key pages
- Offline page or offline-friendly content
- Fast on mobile: passes Core Web Vitals
- Install prompt explained clearly to users
- Push notifications only with clear consent and value
- Tested on Android Chrome and iPhone Safari
Costs and timelines
Because a PWA is a website with extra capabilities, adding PWA features to an existing modern site can be a matter of weeks. Building a new PWA product typically costs less than building separate iOS and Android apps, though complex offline sync or integrations add effort. See our guide to how much a mobile app costs for comparison.
A worked example: a field service PWA
A heating engineering company wants engineers to see job details, take photos and capture signatures on site, often in basements with poor signal.
| Requirement | How a PWA handles it |
|---|---|
| Works with weak signal | Service worker caches the day's jobs; changes sync when back online |
| Photos and signatures | Camera access and touch input in the browser |
| Easy rollout | Engineers install from a link; no app store approval |
| Updates | Every engineer gets fixes instantly |
| Office dashboard | The same codebase serves a desktop view |
A native app would offer deeper device integration, but for this internal tool a PWA delivers what's needed at lower cost and with faster updates.
Measuring PWA success
| Metric | Why it matters |
|---|---|
| Install rate | How many visitors add the app to their home screen |
| Repeat visits | Whether installed users return more often |
| Offline sessions | Whether offline support is being used |
| Load time on repeat visits | The speed benefit of caching |
| Push opt-in and engagement | Whether notifications add value |
| Conversions | Whether the app-like experience improves results |
Track installs and repeat usage separately from your website analytics so you can see whether the PWA features are earning their keep.
How we help
We build PWAs, cross-platform apps and native apps, and recommend one after understanding your users and features. Explore our iOS and Android app development service, or start with a free AI Project Blueprint for a scope and timeline.
The short version
A PWA is a website that installs, works offline and can send notifications, from one codebase that search engines can index. It's ideal for internal tools, ordering, content and MVPs. Choose native or cross-platform when you need deep device access, background processing or a strong app store presence.
