Many Frameworks – One PWA Solution
summary
Claim: use Workbox to make one production-ready PWA for any framework because Angular/React/Vue only provide basic, often unconfigurable service-worker scaffolding. The demo shows a build-time script using Workbox injectManifest (workbox-build), generating a service worker that pre-caches an app shell cached with hashes, updates when hashes change, and exposes an update event for a UX prompt. It uses runtime caching strategies for API calls, recommends late registration, a kill-switch SW, proper cache headers, and cites Gartner’s 50% PWA prediction by 2020.
AI-written summary · about
chapters (11)
- 0:00PWA introduction
- 2:30What is PWA
- 7:10PWA benefits
- 10:48Browser PWA support
- 15:56Framework drawbacks for PWA
- 18:03Solution requirements
- 23:02Workbox for Service Worker
- 28:47Workbox build integration
- 31:56Service Worker tips
- 38:26Resources and community
- 39:08Q&A
related talks
31mMany frameworks, one PWA solution
26mMany Frameworks – One PWA Solution
39mPWA & Front-end Frameworks
17mHow to build a PWA and stay sane: Introduction to Workbox
30mPWA with PWF
24mPWA All The Things!
47mSending the Angular app into deep, deep offline with Workbox
54mBuilding an Angular PWA: Angular Service Worker or Workbox?
