Multiple ChoiceBeginner 45s
Offline-first sync: conflict-free field types
An offline-first mobile app must merge edits made by two devices while disconnected. Which data modeling choice most reduces the need for user-facing conflict resolution?
Options
- 1Model mutable state as append-only, commutative operations (e.g. add-to-set, increment counter)
- 2Store last-write-wins timestamps on every field and let the server pick
- 3Lock records server-side so only one device can edit at a time
- 4Send full record snapshots and reject the second writer's sync
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.