Making Offline Suck Less with Service Workers
summary
Service workers plus the Cache API let a site intercept and hijack requests over HTTPS, run as an independent thread with install/activate/fetch/terminate states, and require cloning requests before storing responses. Demo uses GitHub Pages and a tiny service-composer library to prefetch and manage resources and shows cache.addAll semantics in the install/activate handlers. Browser support: Chrome 40+ enabled, Firefox behind a flag, Safari absent. The demo caches 649 images totaling 800 MB and continues to work offline.
AI-written summary · about
chapters (11)
- 0:00Offline web apps intro
- 1:07Offline experience importance
- 2:12Service workers explained
- 6:43Service worker lifecycle
- 9:48Registering and debugging
- 13:38Cache management
- 17:10Fetch event demo
- 19:36Pushing SW limits with APOD
- 23:28Caching library with SW
- 25:59Future of service workers
- 26:53Q&A
