Scaling with PWA
summary
Progressive Web Apps cut load times with concrete results: 53% of users abandon sites over 3s, and small speed gains raise conversions (one cited 27% lift; 2% more revenue for 5s vs 19s load). The stack is a web app manifest, an application shell cached for instant first paint, and a background service worker (use Workbox to precache and route assets). Case studies: AliExpress sees +104% cross‑browser and +82% iOS conversion, Conga reports ~92% less initial data vs native. Push enables re‑engagement.
AI-written summary · about
chapters (21)
- 0:00Start
- 5:12Challenges of the web
- 6:44So what's the solution?
- 7:20What are Progressive Web Apps?
- 8:55Why build a Progressive Web App?
- 14:35The Web App Manifest
- 21:02What is a Service Worker?
- 23:26Dos and Don'ts of a Service Worker?
- 25:55Service Worker Lifecycle: Registration
- 27:42Service Worker Lifecycle: Installation
- 27:53Service Worker Lifecycle: Activation
- 28:25What is Application Shell?
- 31:25Fetch Events
- 33:44What is Workbox?
- 34:22Workbox Usage
- 35:51Workbox Config
- 36:25After bundling with workbox.config.js
- 37:30What are Push Notifications?
- 38:10Workflow of a typical Push Notification
- 41:03Conclusion
- 41:30QUESTIONS?
