When a connection drops, a displayed record, a local change and a completed server action are different states. The interface should make that distinction clear.
This guide does not assume an application supports offline work. Decide which actions can continue, wait or remain unavailable, then demonstrate the actual behaviour.
Classify the actions
- Viewing previously loaded information
- Preparing a draft
- Submitting a server record
- Payments or orders requiring confirmation
- Several users changing the same record
A single generic connection warning may not explain all these cases. A draft might remain on the device while an order needs a server response.
Show accurate states
Local draft, waiting to send, saved on the server and outcome unconfirmed should not all look like success. Pressing a button is not proof that the intended record exists.
If an important action has an uncertain result, provide a status check before inviting repeated submission. The product team should define how duplicate actions are prevented.
Review reconnection behaviour
- Keep pending work visible.
- Explain each submission result.
- Test for duplicate records.
- Define a route for conflicting edits.
- Offer an appropriate retry or support option.
Automatically choosing between conflicting information is not always appropriate. Some workflows need a user or authorised staff member to resolve the difference.
Test the interruption points
Disconnecting before an action differs from losing connectivity during submission. Include both, as well as closing and reopening the app and checking retained drafts.
Use a suitable test environment and sample data. Do not experiment with live payments or customer actions. If local storage is supported, review security and access separately.
Common questions
Can every app work offline?
No. The supported scope depends on its functions and architecture.
Should I immediately submit again after an error?
Check the state first when the original outcome is uncertain.
Discuss your offline requirements through the BE Soft English website.
