Progressive Web Apps launched as concept a year ago. Now we have case studies: Flipkart (India), AliExpress (China), Washington Post (US) all report significant metric improvements after building PWAs. The data suggests PWAs work—but the adoption pattern is interesting.
PWAs are succeeding most where app stores create most friction.
The Results Are In
Companies publishing PWA metrics:
Flipkart Lite (India e-commerce):
- 70% increase in conversions
- 3x time spent on site
- 40% re-engagement rate
- Works well on 2G networks
AliExpress (Chinese e-commerce):
- 104% increase in conversion for new users
- 82% increase in iOS conversion
- 2x page visits per session
Washington Post:
- 5x faster load times
- 88% improvement in load time
- Better engagement metrics
These are substantial. Not marginal improvements—order of magnitude better user experiences.
Why PWAs Work in Emerging Markets
The pattern is clear: PWAs show biggest impact in India, China, Southeast Asia, Africa. These markets share characteristics:
Limited storage: Low-end phones with 4-16GB storage. Users reluctant to install apps.
Slow networks: 2G/3G common. App downloads expensive (literally—data costs money).
Network unreliability: Offline capability matters more where connectivity is spotty.
Install friction: Every app install prompts reconsideration. PWAs skip install.
In these contexts, PWAs eliminate friction native apps impose. The "instant" web beats "download 20MB app first."
Why PWAs Are Slower in US/Europe
Conversely, PWA adoption in developed markets is slower:
Fast networks: 4G/5G reduce native app download pain. 20MB app downloads in seconds.
App Store trust: Users trust App Store, worry about web apps (justified or not).
Abundant storage: 64-256GB phones make app install trivial.
Platform integration: Native apps integrate better with OS (notifications, sharing, etc.).
PWAs solve problems developed markets don't have as acutely.
The iOS Problem
PWAs work best on Android. iOS support is weak:
No service worker support (as of mid-2016). Offline doesn't work.
No install prompt. Users must manually "Add to Home Screen."
Limited API access. Push notifications, background sync—none of this works.
Apple's lack of support isn't accidental. PWAs compete with App Store (and its 30% revenue cut). Apple has financial incentive to keep PWAs limited.
This kills PWA viability in US/Europe where iOS is ~50% market share. Apps need to work on both platforms or you're excluding half your users.
The Service Worker Maturity
Service workers (PWA's foundation) are maturing:
Browser support:
- Chrome: Full support
- Firefox: Full support
- Opera: Full support
- Safari: None
- Edge: In development
Developer experience:
- Tools improving (Workbox coming)
- Patterns emerging (cache strategies, update flows)
- Debugging still challenging
Service workers are production-ready on Android. iOS is blocker for universal deployment.
What "Progressive" Really Means
"Progressive" is key: PWAs work everywhere, enhance where possible.
Basic experience:
- Fast loading website
- Works offline via cached content
- Responsive design
Enhanced experience (Android):
- Installed to home screen
- Push notifications
- Background sync
- Full-screen mode
This graceful degradation is smart. PWAs don't require cutting-edge browser features—they enhance when available.
The Business Case
PWAs are compelling economically:
Lower development cost: One web app vs separate iOS/Android apps
Instant updates: Push changes without app store approval
No app store fees: No 30% to Apple/Google
Better discovery: URLs are shareable, indexable, linkable
Lower distribution cost: No bandwidth cost for downloads
For e-commerce and content sites, these economics make sense. For gaming or apps requiring native features, less so.
The Manifest File Power
Web App Manifest describes app metadata:
{
"name": "My PWA",
"short_name": "PWA",
"start_url": "/",
"display": "standalone",
"background_color": "#ffffff",
"theme_color": "#000000",
"icons": [...]
}This makes web apps behave like native: full-screen, themed splash screen, appears in app launcher.
Combined with service worker, this blurs web/native boundary significantly.
Real-World Implementation Challenges
Building PWAs isn't trivial:
Offline strategy complexity: Deciding what to cache, when to update, how to handle failures is hard.
Testing: Service worker bugs are subtle. Testing offline scenarios is tedious.
HTTPS requirement: Service workers require HTTPS. This is barrier for some.
Performance tuning: Making apps fast on 2G requires serious optimization work.
Push notification UX: Getting permission prompts right is tricky. Users hate bad prompts.
These aren't insurmountable but they're real work.
When PWAs Make Sense
PWAs work well for:
- E-commerce (Flipkart, AliExpress success)
- News/content sites (Washington Post)
- Travel sites (booking, flights)
- Social media platforms
- Web-based productivity tools
PWAs are questionable for:
- iOS-only user bases
- Apps requiring advanced native features
- Complex offline requirements (beyond caching)
- Gaming (performance limitations)
Looking Forward
PWA adoption will continue growing, but unevenly. Expect:
Strong growth in emerging markets where mobile web dominates
Slow growth in developed markets until iOS supports service workers
More case studies as companies measure PWA impact
Tooling improvements making PWA development easier
Possible Apple support (if regulatory or competitive pressure)
PWAs aren't replacing native apps universally. They're another deployment option with specific trade-offs. In markets where those trade-offs favor PWAs (emerging markets primarily), they're succeeding.
Resources:
