Offline Mode, Online Impact
summary
Claim: offline first apps must make the local DB the single source of truth, queue actions locally, and sync in background using versioned diffs so conflicts merge or prompt manual resolution. Implements local storage with Hive / Isar / drift / sqflite, connectivity checks with connectivity_plus, and periodic sync via workmanager background sync. Presenter shows a working offline blocks game and a journal flow that saves locally and later syncs. Warning: lack of offline support drives roughly 20–60% higher uninstall risk.
AI-written summary · about
chapters (20)
- 0:00Offline mode importance
- 1:50Offline use cases
- 2:33Developer advocacy insights
- 4:59Speaker introductions
- 6:23Flutter offline overview
- 7:48Offline first applications matter
- 10:59Offline functionality features
- 13:07Offline-first design
- 16:04AI offline integration
- 18:53AI frameworks and testing
- 20:39Offline-first architecture
- 22:23Trust in offline apps
- 24:49UI signals and data trust
- 25:10Data sync challenges
- 29:46Local DB setup and conflicts
- 31:54Offline sync challenges
- 33:19Offline dev best practices
- 35:33Security and network awareness
- 37:21Key takeaways and user delight
- 38:46Demo and closing
related talks
22mRapid Development on Offline First Data Sync
31mBrowser database for offline application use
01h 02mPanel 1: Offline
34mOffline-First Mobile App Design
32mOnConnectionLost - The Life of an Offline Web Application
43mOffline-first Architecture - How to survive without the internet?
35mHow Offline-First Architecture Could Save Your Apps
28mOffline first applications in React Native done well