Offline Second
summary
Adds offline mode to a legacy AngularJS app in one month by implementing a Service Worker via Workbox, routing all network calls through a single request facade and a circuit-breaker to detect bad connections, and caching ~30–40 MB of domain data in IndexedDB with a user-triggered “cache” button. Does not implement full bidirectional sync; instead it postpones complex merge logic and only pushes local UI preferences to the server when online, yielding PWA behavior and a reported production revenue lift of up to 5%.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 5:58Legacy apps and business needs
- 10:15Legacy code rules and limits
- 12:47Offline mode definition and implementation
- 17:24Slow/unreliable connections
- 21:35Service Worker and its features
- 24:22HTTPS and mixed content issues
- 26:51Service Worker activation and updates
- 29:19Workbox and caching strategies
- 35:42Custom caching for complex cases
- 38:11Storing large client-side data
- 41:26Data loading and caching strategy
- 43:35Moving logic to client and data adapters
- 47:35Data sync and conflict resolution
- 50:29Cross-device sync technologies
- 53:22Sync protocols and libraries overview
- 54:25Project results and business impact
- 55:55Q&A
related talks
41mOffline Web Apps don't exist anymore!
37mOffline web applications don't exist anymore!
38mSending your Angular App into deep, deep offline with Workbox
52mOffline web applications don't exist anymore!
47mSending the Angular app into deep, deep offline with Workbox
41mIntroduction to Offline First Web Applications
21mOffline first in Angular
22mOffline Angular app in action