Reconcile conflicting edits and large photo uploads without losing submitted inspections.
Backend and product engineers designing software behavior.
Your approach: Use diagrams, tables or prose for customer contracts, state transitions and data ownership; include APIs only to the depth the question requests.
Design an offline-capable field-inspection service. Inspectors edit a checklist and attach photos on mobile; supervisors can correct the same inspection in the web app. Define which conflicts are safe to merge and which need a human decision.
Declare the supported offline duration, including queued writes and retained sync history.
Required target: ≥ 48 hours
Corrections must not silently replace accepted evidence.
Do not silently discard conflicting checklist values based only on device timestamps.
An interrupted upload must not require replaying every photo or expose another inspection’s files.
Define client operations, server acknowledgements, cursors, retries and tombstone retention.
Work through same-field edits, attachment additions and a correction after sign-off.
Describe revision history, authorization and staged/resumable photo attachment.
Calculate daily photo volume and an offline reconnect burst; state quotas and recovery behavior.