Idemnity in the Data Layer
summary
Implementation of Now in Android data layer shows an offline first app that fetches deltas by model version and writes everything into local storage so screens load without network. It uses SQLite and DataStore for complementary storage, runs a one time WorkManager startup sync with exponential backoff, applies explicit migration versions, and treats repository writes as the single source of truth. Conflict resolution uses server change sets and local merges and the setup demonstrably enables offline navigation and reliable sync.
AI-written summary · about
chapters (12)
- 0:00Idempotency in data layers
- 4:24Local vs network data sources
- 10:11Writing data over the network
- 15:24Local vs network data writes
- 17:17Synchronizing offline devices
- 22:09Writing to local data source
- 23:34WorkManager for startup sync
- 25:27Data versioning for changes
- 29:44Offline-first app design
- 31:58Fetching updates and consistency
- 34:04Resolving data conflicts
- 35:00Database sync performance
related talks
39mIndemnity in the Data Layer
06mCreate offline-first apps
36m“Make your app work perfectly offl…” — Connection Interrupted
23mDesigning for Disconnection- The Mental Model of Offline Apps
38m"Offline" is not an error
42mAndroid Application Architecture
25mNo Internet? No Problem!
39mOffline Applications With Architecture Components, Retrofit, Room, Dagger, RxJava