Offline first Flutter applications
summary
Built a Flutter desktop+mobile task app that moves from unreliable Firebase persistence to an interim in‑memory Redux store and finally to a REST backend with Firebase Cloud Messaging for pushes, a repository as source of truth, per‑node timestamp conflict resolution, Drift (formerly Moor) for local reactive SQL, and flutter_cache_manager/cached_network_image for files. Firebase persistence proved inconsistent; the final stack handles offline reads/writes and sync reliably for the app’s use cases though timestamps are a pragmatic, not perfect, conflict strategy.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 3:57What offline first means
- 8:34Firebase offline persistence issues
- 11:44Choosing local storage solutions
- 16:45Caching images and files
- 19:17Summary and key takeaways
related talks
42mGoing Offline first with Flutter
33mSurviving Network Failures: Building Resilient Offline-First…
29mPowering offline-first forestry in Europe's wilds
28mFlutter App Implementation Seen in Code
38mSimpler state management with Dart on the server and synced databases
50mZero to app: Livecoding a cross platform app with Firebase and Flutter
41mThe Flutter journey from a Personal App to a Successful Production App
29mArchitecting the Reactive App with Flutter