One-Line Definition
A Progressive Web App (PWA) is a website built with modern web technologies that behaves like a native mobile app — it can be installed on a user's home screen, load instantly, work offline, and send push notifications — all without going through an app store.
Real-Life Analogy
Think of a traditional website as a pop-up shop: convenient to visit, but it disappears the moment you close the tab, and it's useless if the street (your internet connection) is blocked.
Think of a native app as a brick-and-mortar store: always there, always stocked, but you had to apply for a permit (app store approval), pay rent (development and maintenance costs), and customers must physically walk to your location (download and install).
A PWA is like a food truck that also delivers. It shows up wherever your customers are (the open web), but once they've visited once, it parks permanently on their home screen. It keeps serving even when the roads are closed (offline mode), and it can ping customers directly when something new is on the menu (push notifications). No permit required.
Core Formula
A PWA is not a single technology — it's a combination of three architectural layers working together:
PWA = HTTPS + Service Worker + Web App Manifest
| Component | Role | What It Enables |
|---|---|---|
| **HTTPS** | Secure transport layer | Required for service workers and trust signals; Google confirms HTTPS as a ranking signal |
| **Service Worker** | JavaScript proxy between browser and network | Offline caching, background sync, push notifications, intercepting network requests |
| **Web App Manifest** | JSON file describing the app | "Add to Home Screen" prompt, custom icons, splash screen, standalone display mode (no browser chrome) |
Remove any one of the three and you have an ordinary website. Add all three and the browser treats your site as an installable application.
Comparison with Related Terms
| Dimension | Progressive Web App | Native App | Responsive Website | Hybrid App (e.g., React Native, Ionic) |
|---|---|---|---|---|
| **Installation** | Via browser prompt, no store | App Store / Google Play | None | App Store / Google Play |
| **Offline support** | Yes (service worker cache) | Yes (full) | No (unless manually built) | Yes |
| **Push notifications** | Yes (iOS 16.4+, Android) | Yes | No | Yes |
| **Device API access** | Partial (camera, geolocation, Bluetooth, but limited) | Full | Limited | Near-full |
| **Update mechanism** | Instant, server-side | Store review (1–7 days) | Instant | Store review |
| **Typical build cost** | 1 codebase | 2–3 codebases (iOS, Android, web) | 1 codebase | 1 codebase + native wrappers |
| **Discoverability** | Search engines + URL | App store search only | Search engines | App store search only |
| **Storage footprint** | A few MB (cached assets) | 30–200 MB typical | Negligible | 20–100 MB |
Key distinction: A responsive website adapts its *layout* to screen size. A PWA adapts its *capabilities* — it can function without a network, live on the home screen, and re-engage users through notifications. A native app is compiled for a specific operating system. A hybrid app wraps web code inside a native container, whereas a PWA *is* the web, enhanced.
Use Cases
1. E-commerce storefronts. Alibaba's PWA increased conversions by 76% and cut bounce rates, while Flipkart's PWA tripled time-on-site. For cross-border sellers, a PWA removes the friction of app-store downloads in markets where users are data-conscious and storage-constrained.
2. Content and media platforms. Twitter Lite (now X Lite) reduced data usage by 70% and increased pages per session by 65%. News sites use PWAs to cache articles for subway commutes and push breaking-news alerts.
3. SaaS dashboards and internal tools. A CRM or inventory tool built as a PWA can be installed by warehouse staff on cheap Android devices and continue working in dead zones.
4. Travel and booking. Airlines like KLM use PWAs so travelers can access boarding passes offline — critical when roaming charges or airport Wi-Fi fail.
5. Emerging-market-first products. In regions where average app download sizes exceed monthly data budgets, a 2 MB PWA versus a 100 MB native app is the difference between adoption and abandonment.
Misconceptions
"A PWA is just a responsive website." No. Responsiveness is a *design* property. A PWA requires service workers and a manifest to be installable and offline-capable. A responsive site without those is not a PWA.
"PWAs work identically on iOS and Android." Not quite. Android (Chrome) has supported the full PWA stack since 2015. iOS Safari added service worker support in 2017 (iOS 11.3) and push notifications only in iOS 16.4 (March 2023) — and even then, only for apps added to the home screen. Always test both platforms.
"PWAs replace native apps entirely." For content, commerce, and lightweight tools, often yes. For apps needing heavy background processing, advanced hardware access (e.g., ARKit, complex Bluetooth), or App Store distribution as a growth channel, native still wins.
"PWAs can't be listed in app stores." False. Microsoft Store, Google Play (via Trusted Web Activity), and even the App Store (via wrappers) accept PWAs, though policies vary.
"Offline mode means the whole app works offline." It means *whatever you cached* works offline. Dynamic, personalized, or real-time data still requires a connection or a background sync strategy.
"PWAs are automatically SEO-friendly." PWAs are still websites, so standard SEO applies — but service worker caching can interfere with crawlers if misconfigured. Use server-side rendering or dynamic rendering where needed.
Related Terms
- Service Worker — the background script that powers offline caching and push.
- Web App Manifest — the JSON file that makes a site installable.
- Single Page Application (SPA) — a common architectural pattern for PWAs, though not required.
- Headless Commerce — often paired with PWAs to decouple frontend from backend.
- Trusted Web Activity (TWA) — the technology that lets a PWA be published on Google Play.
- Lighthouse — Google's auditing tool that scores PWA compliance.
- App Shell Model — a caching architecture where the UI shell loads instantly and content streams in.
- Workbox — Google's library for simplifying service worker logic.
Bottom line for DTC operators: A PWA is the closest thing the open web has to a native app — installable, offline-capable, and push-enabled — without the app-store tax or the two-codebase maintenance burden. For cross-border sellers targeting mobile-first, data-sensitive markets, it is often the highest-ROI frontend investment you can make.