Designing Offline Applications for the Enterprise
summary
SAP mobile service plus Android SDK implements an OData-based offline sync that downloads an initial dataset, applies delta download via server or middleware hash comparison, and stores data in two on-device databases (entity store and request store). It creates a request queue with ordered, mergeable requests, performs local key mapping to replace placeholders with server keys, uses ETag checks for conflicts, and claims enterprise encryption and an ultra database up to 16 GB. Demo shows local CRUD, offline operation, and successful sync with repeatable‑request and request‑optimization handling.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:50Offline complexity overview
- 4:20SAP mobile service architecture
- 5:44OData protocol basics
- 8:35Offline data technology
- 11:25Initial data download
- 12:56Delta sync mechanisms
- 17:12Local query and update
- 20:27Key mapping and error handling
- 24:00Concurrency and data integrity
- 25:30Advanced offline features
- 28:40Repeatable requests
- 29:45Request optimization
- 34:25Offline demo walkthrough
- 35:07Live offline app demo
- 39:32Q&A session
related talks
23mDesigning for Disconnection- The Mental Model of Offline Apps
39mOffline Applications With Architecture Components, Retrofit, Room, Dagger, RxJava
06mCreate offline-first apps
37mIdemnity in the Data Layer
36m“Make your app work perfectly offl…” — Connection Interrupted
38m"Offline" is not an error
38mThe real case of offline-first app: Farmer App…
25mNo Internet? No Problem!