Tame your service worker [...]
summary
Explains concrete service worker practices: service workers act as a network-programmable proxy and cause first-load blocks if registered too early, so register after critical assets load; rescue broken workers by deploying an empty worker that calls skipWaiting and clients.claim to force updates; precache carefully because cache.addAll fails on 404/500 and opaque cross-origin responses, and storage is limited so check storage estimation API; recommends generators and tools like Workbox, PWAbuilder and Lighthouse and notes broad browser/Windows Store support.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:15After all, what is PWA?
- 4:23Cross-platform?
- 8:04UX advantages?
- 10:54Know your toolset
- 13:11Registration
- 13:28Background syncronization
- 18:44Rescue plan
- 25:01Storage is not unlimited
- 26:05Opaque responses limitations
- 31:07Default prompt
- 32:28Show native prompt
- 32:39Open questions
related talks
42mService Worker: Taking the Best From the Past Experience for The Bright Future of PWAs
42mHow Do Service Workers Even?
27mAnd Now You Understand Service Workers
45mThe perfect Service Worker. How to design it?
32mThe ServiceWorker is coming, look busy
30mBuilding Faster, More Resilient Apps with Service Worker: A Caching Strategy Deep Dive
51mAutomating a service worker with Workbox 6
05mLightning talk: Service Workers, use them