Let’s Sync Up! Tips and Tricks to Add Offline Sync to Your App with Confidence
summary
Shows a concrete migration from many small calls to a single offline endpoint—6000 requests down to 1—and argues for designing separate sync endpoints, packing only needed fields, and syncing assigned or role‑scoped items. Recommends Room/relational stores for complex data, contrasts Realm, and suggests Jetpack WorkManager for background work and silent push notifications for efficient updates. Pushes server authority: use server‑managed unique IDs and let the server resolve collisions.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:07Why Offline Sync
- 3:22Key Workflow
- 5:26Offline Functionality
- 8:17Create Separate Endpoints
- 10:29Store the Data You Need
- 12:48Update Only Modified Records
- 13:54File Storage
- 15:40Background Sync
- 16:40Update Notification
- 20:14Primary Keys
- 24:03Push Data
- 24:35Avoid Complexity
- 28:12Offline First
- 30:22Wrap Up
related talks
39mSay Hello to Offline First
36mTesting Offline First Mobile Applications
31mI'm offline, cool! What now?
42mThe Challenges of Offline Work in Mobile
32mLook, Mum, No Internet - Creating great experiences with offline-first apps
38m"Offline" is not an error
45mOffline First (Web) Apps
42mGoing Offline first with Flutter