Build an interactive laboratory that demonstrates how mobile and web applications behave when users edit the same records offline and reconnect later.
Create a simulated environment with three devices, each holding a local copy of the same dataset.
Users should be able to:
Disconnect and reconnect individual devices.
Edit, delete, and restore records on different devices.
Change the order in which synchronization events arrive.
Introduce delayed messages, duplicate requests, and interrupted sync operations.
Compare last-write-wins, field-level merging, version-vector-inspired conflict detection, and manual resolution strategies.
Display a visual timeline showing local edits, queued operations, server acknowledgments, conflicts, and resolved records.
Include a conflict inspector that explains exactly why two changes collided and what information each resolution strategy preserves or loses.
Provide deterministic replay, reset controls, test cases for simultaneous edits and duplicate delivery, and exportable event logs.
Use a clearly documented synchronization model rather than pretending the simulation represents every distributed system. Make the tool useful for engineering teams designing offline-first applications, and keep all demonstration data local unless the user explicitly configures a backend.
0 Comments