The Promise That Was, and What Remains
Progressive Web Apps were pitched as a way to get app-like experiences — offline support, push notifications, home screen installation — without the overhead of native app development and app store distribution. Years later, the picture is more nuanced than the original pitch suggested.
Where PWAs Genuinely Shine
Content-focused apps, internal business tools, and products where reaching the widest possible audience with a single codebase matters more than deep platform integration are excellent PWA candidates. A service worker enabling offline access and a manifest enabling home screen installation cover most of what these use cases actually need.
The iOS Limitation That Still Matters
Safari’s support for PWA capabilities — particularly push notifications, which arrived years later than on other platforms, and background sync — has historically lagged behind Chrome and Android. This gap has narrowed but hasn’t disappeared, and it remains the most common reason teams choose native or React Native over a PWA for iOS-heavy user bases.
Discoverability Remains a Real Trade-off
PWAs don’t appear in app stores by default, which means losing app store search as a discovery channel — a meaningful loss for consumer apps that rely on organic app store traffic. This matters far less for apps distributed primarily through a website, marketing, or existing user relationships.
When Native or Cross-Platform Still Wins
Apps needing deep OS integration — background location tracking, complex Bluetooth device communication, camera-intensive features, or the polish of platform-specific UI conventions — still generally need native or cross-platform framework capabilities that PWAs can’t fully replicate through web APIs.
The Honest Recommendation
PWAs remain a genuinely good choice for content sites, internal tools, and products where “good enough” mobile experience with zero app store friction beats a more polished but higher-effort native app. They’re not a universal replacement for native development, and treating them as one leads to disappointing results for use cases they were never well suited for.