No Signal, No Problem: How We Collect Data in the Most Remote Places
summary
Shows concrete fixes used in IASO by Bluesquare for syncing months of field data over days or weeks of intermittent connectivity, including an offline-first distributed app model, a zip bootstrap bundle that cuts download time for 20–50 tablets, and an insert-or-update DAO that avoids Room’s replace+cascade data loss. Explains foreign‑key diagnostics that surface the offending ID, uses OkHttp gzip, Retrofit + Moshi for compact transfers, and reports that these techniques reliably preserve and sync collected records.
AI-written summary · about
chapters (10)
- 0:00Remote data collection challenges
- 1:08Carmen Sandiego game analogy
- 3:22ODK and Yazoo tools
- 4:27Local data storage in Yazoo
- 6:02Foreign key exceptions offline
- 10:05Refreshing data with poor internet
- 11:56Avoiding data loss on conflict
- 14:31Compressing data for downloads
- 16:24Retrofit and Moshi backend
- 50:30Q&A
related talks
25mNo Internet? No Problem!
37mLet’s Sync Up! Tips and Tricks to Add Offline Sync to Your App with Confidence
37mIdemnity in the Data Layer
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
38mThe real case of offline-first app: Farmer App…
42mThe Challenges of Offline Work in Mobile
41mOffline First
36m“Make your app work perfectly offl…” — Connection Interrupted
