Many business apps are mostly forms: orders, field visit reports, attendance, service requests. In places where mobile data drops in and out, a form that fails on submit loses work and frustrates users. Here is the checklist we use when building forms for field staff and customers.

1. Save drafts locally as the user types. Store form state on the device (for example with SQLite, Hive or AsyncStorage) so closing the app or a phone call does not wipe it.
2. Queue submissions. If there is no connection, save the submission in a local queue and show "Saved, will send when online". Retry in the background when the network returns.
3. Make submissions idempotent. Generate a unique ID on the device for each submission. The server can then ignore duplicates when a retry sends the same record twice.
4. Compress photos before upload. Resize camera images on the device. A full-size photo is often the reason a submit times out.
5. Show clear status. Mark each record as draft, pending or sent. Users should never wonder whether their work reached the office.
6. Validate on the device. Check required fields and formats before submit, so users fix errors without waiting for a server response.
7. Test with throttled networks. Use the emulator's network settings or a slow real connection, and test switching to airplane mode mid-submit.

These steps add some work early on, but they prevent the most common complaint from field users: "I filled it and it disappeared."