Progressive Web App (PWA)
A web application that uses modern web APIs to provide a native app-like experience, including offline support, push notifications, and device installation.
Detailed Explanation
PWAs combine the reach of the web with the capabilities of native apps. They are built with standard web technologies (HTML, CSS, JavaScript) but use service workers for offline support, manifest files for installation, and push notifications for engagement.
Key PWA features: installable (add to home screen), offline capable (works without internet), push notifications (re-engage users), fast (cached shell loading), and secure (HTTPS required). PWAs eliminate the need for app store distribution while providing native-like capabilities.
Why It Matters
PWAs provide native app experiences without app store overhead. They are faster to develop, easier to update, and reach users directly through the browser.
Real-World Example
Twitter Lite is a PWA that loads in under 3 seconds on 3G, works offline, sends push notifications, and takes 70% less data than the native app. Users can install it directly from the browser.
When to Use
When you want native app features without app store distribution, when targeting users on slow networks, or when you need to reduce development and maintenance overhead across platforms.
Advantages
- No app store distribution needed
- Works across all platforms with one codebase
- Offline support via service workers
- Push notifications for engagement
- Automatic updates without user action
Disadvantages
- Limited access to native device APIs
- No app store visibility/discoverability
- iOS support is less mature than Android
- Service worker complexity
- Push notification support varies by platform
Frequently Asked Questions
What makes a web app a PWA?
Three requirements: HTTPS (security), a web app manifest (installability), and a service worker (offline support). Additional features like push notifications and fast loading enhance the PWA experience.
Can PWAs replace native apps?
For many use cases, yes. PWAs work well for content apps, e-commerce, and productivity tools. Native apps are still needed for heavy gaming, AR/VR, and apps requiring deep OS integration.
How do I build a PWA?
Start with a web app, add HTTPS, create a manifest.json (icons, name, theme), register a service worker (caching, offline), and optionally add push notifications. Frameworks like Next.js and Nuxt have PWA plugins.
Do PWAs work on iOS?
Yes, with limitations. iOS supports service workers and home screen installation but does not support push notifications (as of iOS 16.4+, limited support). PWAs on iOS are essentially bookmarked web apps with offline support.
Are PWAs SEO friendly?
Yes. PWAs are regular websites that search engines can crawl. They are indexable, linkable, and shareable. This is an advantage over native apps, which are not searchable by web search engines.