Offline First (Web) Apps
summary
Argues for an offline‑first architecture: keep a local copy of user data in a local browser datastore, funnel all writes through a sync engine (demo uses Hoodie + CouchDB and mentions serviceworker/appcache/PhoneGap/Electron), shows a to‑do app that continues working when the server stops and then automatically re‑syncs when it returns, and a prototype that stores offline maps and photos on a four‑year‑old Android, proving robustness and much faster perceived performance.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:27Detour: The power of boxes
- 4:00Critique of future visions
- 7:25Normality versus perfection
- 12:30The case for offline first
- 16:19Architecture and syncing
- 20:18Implementation demonstration
- 26:02Distributed systems insights
- 29:02User experience opportunities
- 35:38Design and UI challenges
- 40:34Conclusion and summary
related talks
39mSay Hello to Offline First
41mOffline First
30mOffline First: Making Your App Awesome When the Network Isn't
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
44mDesign principles and implementation strategies for better offline experience
38mHow we developed an Offline‑First app using Persistent Storage
31mI'm offline, cool! What now?
29mGive Apps Online Superpowers by Optimizing them for Offline
