Increasing User Access through Service Workers
summary
A mobile attendance app is under development for Kakuma refugee camps and it actually runs in very spotty networks — 3G everywhere surprised the team — but many devices never get OS updates so only about 50% on Android 4.0+ can use modern browsers. Service workers are adopted as progressive enhancement: written from scratch (Workbox optional), tackled lifecycle and cache-validation problems, and deployed with strategies like a no-op service worker, feature flags and force-update hooks so updates and emergency rollbacks work in the field.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:45Battery Usage
- 5:08Offline Capabilities
- 9:13Progressive Enhancements
- 11:28What Is a Service Worker
- 13:25Understanding the Life Cycle of a Service Worker
- 14:41Install the Service Worker
- 17:19Redundancy
- 17:39Tips for Starting
- 19:46No Op Service Worker
- 20:26Resources
- 22:06What Dev Tools You'Re Using for Service Workers
- 23:30What Is the Main Reason To Do Web App Using Service Workers Instead of Native App
related talks
55mThe Future of the Mobile Web
40mHow to Make a Mobile Web App Better with Browser APIs
42mService Worker: Taking the Best From the Past Experience for The Bright Future of PWAs
29mPWA, Hidden Stories about future of the Web - II
32mCross-platform Progressive Web Apps
01h 00mService Worker: Bringing Native App Experience to Web Apps
38mWhat Service Workers can do
25mOffline-enabled Web Apps