The real case of offline-first app: Farmer App…
summary
An Android app for Ghanaian farming communities stores user inputs as draft records in a separate Room table, shows local data via Room flows immediately, and pushes drafts with unique WorkManager jobs when connectivity returns; images are prefetched and cached to disk with Coil (configured to use ~50% disk cache) and retried until successful; GPS-only LocationManager replaces FusedLocationProvider for stable offline field mapping, and forcing an initial online map load preserves offline polylines.
AI-written summary · about
chapters (12)
- 0:00Farmer App project
- 1:05Ghana farmer challenges
- 2:11Offline-first app
- 3:14How Farmer App works
- 3:59Offline read/write strategies
- 8:41Read strategy details
- 9:24Write strategy details
- 18:00Real challenges & solutions
- 18:24Offline images
- 24:30Offline location accuracy
- 32:20Offline map polylines
- 36:47Key takeaways & Q&A
related talks
45mOffline First (Web) Apps
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
43mOffline-first Architecture - How to survive without the internet?
06mCreate offline-first apps
36m“Make your app work perfectly offl…” — Connection Interrupted
15mBuilding Apps for Rural Users in Kenya
38m"Offline" is not an error
44mTransforming Farmer's Lives Using Android in Kenya