Browser support in 2026: nearly universal
The long-running criticism of PWA — "Safari doesn't support it" — is no longer valid. Apple added service worker support in Safari 11.1 (2018), proper push notification support in iOS 16.4 (2023), and has continued expanding capabilities since. The current landscape:
| Browser | Service Worker | Web Push | Install prompt | Market share |
|---|---|---|---|---|
| Chrome (Android/Desktop) | ✅ Full | ✅ Full | ✅ Full | ~65% |
| Samsung Internet | ✅ Full | ✅ Full | ✅ Full | ~6% |
| Edge (Windows/macOS) | ✅ Full | ✅ Full | ✅ Full | ~5% |
| Safari (iOS 16.4+) | ✅ Full | ✅ Installed only | ⚠️ iOS-style only | ~19% |
| Firefox (Desktop) | ✅ Full | ✅ Full | ❌ No install UI | ~3% |
| Opera / Brave | ✅ Full | ✅ Full | ✅ Full | ~2% |
97%+ of global browser traffic now runs on a browser with full service worker support. For web push specifically, Chrome + Samsung Internet + Edge alone cover over 75% of mobile users. The "but iOS doesn't support it" objection applies only to the install prompt UX, not the core capabilities.
Major brands betting on PWA at scale
The most telling signal of PWA maturity is who's using it. These aren't experimental projects:
Starbucks
98.84% reduction in app size. 2× daily active users after PWA launch. Offline menu browsing on low connectivity.
60% reduction in data usage, 40% increase in time spent vs mobile web, 44% increase in user-generated ad revenue.
Twitter / X
PWA (twitter.com) is the primary web client. 65% reduction in page weight, 75% reduction in tweets to page load.
Microsoft Teams
Full Teams web client runs as an installable PWA. Handles video calls, file sharing, notifications — native-parity for most use cases.
Spotify (Web Player)
Installable PWA available on desktop and mobile. Full playback, offline caching of playlists, push notifications.
Uber
Uber Lite PWA targets markets with poor connectivity. 50KB page load on 2G, push notifications for ride updates.
The pattern is consistent: smaller app size, faster loads, better engagement metrics — with one codebase that works everywhere. For no-code makers, these aren't edge cases to aspire to; they're proof that the technology is production-grade.
PWA capabilities in 2026: what's possible
Project Fugu — Google's initiative to close the capability gap between web and native — has shipped over 100 APIs. Here's the capability map that matters for SaaS products:
Device hardware
Camera, Microphone, GPS, Bluetooth (Web Bluetooth), NFC (Web NFC), USB (WebUSB), Serial (Web Serial)
Offline & Storage
Service Worker, Cache API, IndexedDB, OPFS (Origin Private File System), Background Sync, Persistent Storage
OS integration
File Handling, Protocol Handlers, Share Target, Screen Wake Lock, Badging API, Window Controls Overlay
Network & Push
Web Push (FCM), Background Fetch, Periodic Background Sync, Network Information API
Identity & Security
WebAuthn (biometrics), Credential Management, Web OTP, Permissions API
UI & Experience
Install prompt, Scope Extensions, Window Management, Fullscreen, Display Cutout, Screen Orientation
PWA on Google Play: the by-the-numbers view
Trusted Web Activity — Google's method for publishing PWAs on the Play Store — has been production-ready since 2019. In 2026:
- TWA apps are indistinguishable from native apps to Play Store search and users
- App size advantage: a TWA is ~800 KB vs 5–50 MB for a typical native app — meaningful in markets with storage constraints
- Update model: web changes go live immediately without a Play Store review — only changes to the native shell require a new submission
- Policy compliance: TWA passes policy 4.3 when the underlying PWA meets installability requirements
- Alternative: Capacitor V2 — for apps without a full PWA setup. Works with any HTTPS URL. SaasToStore auto-selects based on your PWA checker score
PWA vs native: when to choose which in 2026
The choice isn't binary — it's a function of your product's requirements.
| Dimension | PWA (+ TWA/Capacitor) | Native |
|---|---|---|
| Maintenance | One codebase — update web, app updates | Two codebases (iOS + Android) |
| App store updates | Web content live instantly — no review | Every change = store review (1–3 days) |
| Build cost | 15–79€ one-time or monthly via SaasToStore | 10 000–100 000€ native dev |
| Performance | Excellent for SaaS, dashboards, stores | Required for AR, 3D, heavy animation |
| Hardware access | Camera, GPS, BT, NFC, Biometrics ✅ | Full access to all native APIs |
| Store presence | Google Play, Microsoft, Snap, Flathub ✅ | Google Play, App Store |
| iOS App Store | Not directly (Sprint 6 planned) 🔜 | Full support |
| Offline first | Yes — with service worker | Yes — with native logic |
| Best for | SaaS, dashboards, communities, stores, tools | Games, AR/VR, device-intensive apps |
What's next for PWA: the 2026–2027 horizon
The W3C Web Applications Working Group and browser vendors have several capabilities in active development:
- Web App Scope Extensions — multi-origin PWAs (shipping in Chrome, spec in progress for other browsers)
- Widget API — home screen widgets for PWAs on Android and Windows, without a native app layer
- Tabbed Application Mode — browser-style tabs inside an installed PWA, useful for SaaS multi-document products
- Local Font Access — access the user's installed fonts from a PWA — critical for design tools
- WebGPU at scale — hardware-accelerated 3D graphics in the browser, enabling categories previously impossible in PWA
Each of these, once shipped, flows automatically to apps on Google Play via TWA — without a new store submission. This is the compounding advantage of building on the web platform.
Is your web app ready to become a PWA store product?
The gap between "web app" and "app store product" in 2026 is primarily a packaging and distribution challenge — not a technology gap. If your app is on HTTPS and loads correctly, you're closer than you think.
Free PWA check — know exactly where you stand
Our checker audits manifest, service worker, HTTPS and Lighthouse score in 10 seconds. You'll know immediately which stores you can publish to today.
Check my app →