Progressive Web Apps
summary
Progressive Web Apps use a Web App Manifest plus a Service Worker to control fetches, caching and background sync; real results: Tinder cuts cold-load from 11.91s to 4.69s and PWA is ~90% smaller than native, Uber serves ~50 KB gzipped and loads <3s on 2G, Trivago boosts engagement +150% and clicks +97% with 67% offline browsing, Pinterest raises engagement ~60% and ad revenue +44%. Use Cache API or IndexedDB for offline storage; watch iOS 50 MB limit and auto-delete, and platform API gaps (no DOM, limited native sensors).
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:03What is a PWA?
- 7:14Make your application a PWA
- 8:00What is a Web App Manifest?
- 9:19What is a service worker?
- 15:49Client side data storage
- 17:26What is IndexedDB
- 24:58Offline Support - background sync
- 26:40PWA Limitations
related talks
29mAre Progressive Web Apps the new future?
38mProgressive Web Applications: The What, the Why and the How
29mProgressive Web Apps: What, Why and How?
53mProgressive Web Applications - The best of both worlds (App & Web)
43mThe search for App-iness: building the future with Progressive Web Apps
31mWeb for all The power of progressive web apps
43mProgressive Web Apps - the Return of the Web?
37mIntro to Progressive Web Apps