Offline First
summary
Argues that apps must treat offline as the default and connectivity as an enhancement, showing a concrete stack: a front end that only talks to the hoodie store API, local browser storage syncing to CouchDB via a sync engine, and eventual replication so changes are queued and delivered with eventual consistency. Gives field evidence (Africa trip, ~40-person workshops), examples (rail ticket app failing on trains, people screenshotting views), UI problems (save vs sync, message reordering) and tools and tradeoffs.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:05How we work
- 8:25Normality is imperfect
- 10:28Offline First
- 11:35Offline Architecture
- 26:08App preemption
- 27:28Google Maps
- 28:53Challenges
- 33:02Performance
- 34:47Data
- 40:06Outro
related talks
39mSay Hello to Offline First
45mOffline First (Web) Apps
23mDesigning for Disconnection- The Mental Model of Offline Apps
41mThe UI/UX Benefits and Trade-Offs of Local-First Apps
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
44mDesign principles and implementation strategies for better offline experience
01h 02mPanel 1: Offline
06mI'm Offline, cool. What now?
