The UI/UX Benefits and Trade-Offs of Local-First Apps
summary
Claims that local‑first delivers dramatic latency and offline creation wins, demonstrates a working CouchDB and PouchDB replication flow in a 10-line sync example producing an offline‑capable realtime collaborative to‑do, and reports a decade of practical experience. Concrete tradeoffs include frequent surprising conflicts, the prevalence of last‑write‑wins in many stacks, the unnecessary default to CRDTs, and hard engineering choices: selective syncing, eviction plans, client trust versus server authority, and UX patterns for optimistic updates and manual conflict resolution.
AI-written summary · about
chapters (11)
- 0:00Local-first apps intro
- 2:11How sync engines work
- 5:2610-line sync engine demo
- 9:58CouchDB and PouchDB value
- 12:06Sync conflicts explained
- 17:19Building sync apps advice
- 24:19Local-first UI/UX challenges
- 31:41Optimistic updates handling
- 34:31Sync state communication
- 36:15Conflict resolution trade-offs
- 39:49Conclusion
related talks
41mOffline First
45mOffline First (Web) Apps
39mSay Hello to Offline First
31mI'm offline, cool! What now?
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
33mLocal-first and Sync Engines, the Architecture of the Future?
30mOffline First: Making Your App Awesome When the Network Isn't
42mThe Challenges of Offline Work in Mobile