Say Hello to Offline First
summary
Argues that apps must treat being offline as a normal state and gives a concrete stack and flow: Hoodie + PouchDB + CouchDB makes the client write locally, enqueue tasks, and sync via replication so client and server never talk directly; service workers and web workers handle caching and heavy work while service worker replaces AppCache and supports background sync and push. Mentions storage behavior (browsers prompt at ~50 MB, Chrome computes unlimited) and shows the approach works for multi-device sync and conflict resolution.
AI-written summary · about
chapters (10)
- 0:00The offline first concept
- 3:56Offline-ready UX
- 5:25Rethinking app architecture
- 8:56Decoupling client and server
- 12:45UI for request management
- 14:50Implementing with Hoodie
- 17:42Handling files and appcache
- 20:50Web workers for performance
- 29:05The role of service workers
- 34:36Data management with PouchDB
related talks
41mOffline First
45mOffline First (Web) Apps
31mI'm offline, cool! What now?
44mDesign principles and implementation strategies for better offline experience
30mOffline First: Making Your App Awesome When the Network Isn't
23mDesigning for Disconnection- The Mental Model of Offline Apps
06mI'm Offline, cool. What now?
21mGo Offline First to Save The World