PWA Challenges
summary
Concrete results and gotchas: a PWA is simply HTTPS serviceworker manifest and service workers deliver big first‑paint gains for repeat visits but are hard to measure synthetically. Case studies show real revenue lift (Ola cab smaller than Android install and 20% reclaimed users; Pinterest spikes in signups; AliExpress ~104% new‑user conversion uplift). Tools and patterns: use Workbox, app‑shell, background sync, Payment Request and Credential Management. Watch cache behavior—opaque responses inflate size and can cause cache quota exceeded—and roll PWAs out incrementally (HTTPS → manifest → SW → push → advanced features).
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:30Case Studies
- 4:12Progressive Web Apps
- 6:35Integrated
- 7:40PWA
- 8:30Performance Boons
- 9:32Measuring Service Workers
- 10:22Service Worker Impact
- 11:25Progressive Web Experience
- 13:55The Hype
- 16:18Do we need a PWA
- 18:07How the web cant do
- 25:35Two characteristics to consider
- 29:53Fast and fluid experiences
- 33:44Feeling like an app
- 37:20Cache
- 41:30Beyond PWA
- 43:41Planning
related talks
36mService Workers and their role in PWAs
45mScaling with PWA
49mIntro To Progressive Web Apps
36mPWA underhood: what makes it so progressive
24mPWA for Mobile Engineers
44mPWA - Welcome to the Future
55mPWA Fundamentals: websites with superpowers
17mTransforming your Web Application into a PWA - Why and How?