Article6 min readUpdated
Offline Mode Design: Drafts, Sync and Conflicts
Offline mode design for apps in India: what to allow without internet, sync status indicators, saved drafts and conflict messages, with example wording.
By Tithi Mondal, UI/UX Designer
A field agent for a farm input company stands in a village where the signal comes and goes. He fills a 12-field order form, taps Submit, and the app shows a spinning circle for a minute, then clears the form. The order is gone. He fills it again, and this time he writes it in a notebook as well.
Offline mode is the ability of an app to keep working when the phone has no internet, then update the server once the connection returns. Offline mode design is about three questions. What can the user do without a network? What does the screen say about the state of the data? What happens when the phone and the server disagree? Most Indian users have patchy signal at some time, in lifts, trains and small towns. See designing for low-end phones and slow networks for the wider context. In my agritech work, weak signal is the normal case, not the exception.
Which tasks should work in an app without internet?
An app without internet should allow the tasks that people do most and that do not need live data from the server. Choose these tasks before designing, because each one needs storage, sync and a conflict plan.
| Task | Offline? | Why |
|---|---|---|
| View the last loaded list or order | Yes | Cached data is useful |
| Fill a form or write a note | Yes | Save as a draft |
| Take a photo for later upload | Yes | Queue the upload |
| Pay or transfer money | No | Needs live confirmation |
| Check live stock or delivery tracking | No | Stale data misleads |
| Change a password | No | Needs the server |
Be honest about the limits. A screen that pretends a payment worked offline is worse than one that says "Connect to pay". Also note that data kept on the phone is personal data on a device that can be lost. The business must confirm with its legal or compliance adviser what it may store offline and for how long, and which items need extra protection.
How should the app show that it is offline?
The app should show a calm, persistent message that says it is offline and what still works. It should not block the screen, and it should disappear when the network returns.
- Banner at the top: "You are offline. You can still view saved orders and fill forms."
- Disabled actions explained: a disabled "Pay" button with a line below: "Connect to the internet to pay."
- Last updated label: "Showing data from 10:42 am".
- Return message: "Back online. Syncing your changes." A short toast is enough.
Do not use a red error screen for a normal condition. Use a neutral colour, text and an icon, so that colour is not the only signal. Do not show a full-page "No internet" screen when the user has saved content to look at. Use that full page only where nothing can be shown, and give it a Retry button and a link to saved items. See empty states, loading and error screens.
What does a sync status indicator need to say?
A sync status indicator should say one of four things: saved on this phone, waiting to sync, syncing, or synced. It sits next to each item that can be out of date, not only in a global bar.
Use small labels or icons with text:
- Saved on this phone: "Saved on this phone. Will send when online."
- Waiting: "Waiting for network".
- Syncing: "Sending..." with a small progress indicator.
- Synced: "Sent" with a tick and the time.
- Failed: "Could not send. Tap to try again."
On a list of orders, show a small status on each row, so the user sees exactly which ones have reached the server. At the top, a summary: "3 items waiting to send". Tap it to see the list, with a "Send now" button. Never let a user wonder whether an item is safe. An icon without text will not translate for users who rely on a regional language.
How should saved drafts work?
Saved drafts should store the user's work automatically as they type, and bring it back exactly where they left it. The user should never have to press Save to avoid losing work.
- Autosave: save on every field change or every few seconds. Show "Draft saved" in small text.
- A drafts list: a place to find unfinished items, with a date: "Order for Ramesh, saved today 4:10 pm".
- Return prompt: when the user comes back, show "Continue your draft?" with "Continue" and "Delete draft".
- Submit offline: when a user taps Submit with no network, do not fail. Save the item as "Waiting to send" and say: "Saved. We will send it when you are online."
- Photos and attachments: keep them with the draft and upload them when the network returns, in the background if the platform allows.
Draft deletion needs a confirmation, because a deleted draft cannot be recovered; see pop-ups, modals and bottom sheets. Set a clear rule for how long drafts stay and say it: "Drafts are kept for 30 days." The real period is the business's choice. For long forms, see form design best practices.
What should a conflict message say?
A conflict message appears when the user changed something offline and someone else changed the same thing meanwhile. It should say what clashed in plain words and give 2 or 3 clear choices.
Conflicts are rare if the product is designed well. Reduce them first: let one person own a record, lock records being edited, or merge changes to different fields automatically. When a real clash remains, show a screen like this:
This order was changed while you were offline.
Your change: delivery on Friday.
Their change: delivery on Saturday, by Priya at 3:15 pm.
Which one do you want to keep?
Buttons: "Keep mine", "Keep theirs", "See both". Show the two versions side by side with the difference highlighted. Do not choose silently for the user. Do not use a technical word such as "merge conflict" or "error 409". Ask your developer which kind of conflict is possible in your product, then design only those cases.
Which mistakes break offline experiences?
Offline experiences break when the user cannot trust what is saved. These are the failures I look for first in a design review.
- Clearing a form after a failed submit.
- A spinner that never ends and has no time-out.
- Showing old data with no time label.
- Allowing a payment screen to proceed offline.
- Hiding the queue, so users cannot see what is waiting.
- Sending the same item twice after a retry. The developer must prevent duplicates, and the screen must show one row per item.
- Using the same message for "no network", "server down" and "slow network".
- Never testing on a phone with airplane mode on, or with a throttled network. See usability testing on a small budget.
A simple test: turn on airplane mode, use the app for 5 minutes, turn it off, and check that nothing is lost and every item shows its status.
If your users work in weak-signal places, I can map the offline states with you as part of a mobile app design project, or you can reach me through the contact section.
Frequently asked questions
Does every app need an offline mode?
No. Apps that depend on live data, such as payments or tracking, need clear offline messages more than full offline use. Apps used in weak-signal places gain the most from saved drafts and queued sync.
How do I show that data is waiting to sync?
Show a small label on each item, such as Waiting for network, and a summary at the top such as 3 items waiting to send. Update the label to Sent when the server confirms.
What is a sync conflict?
A sync conflict happens when the same item was changed on the phone and on the server while the phone was offline. The app should show both versions and let the user choose.
Should a payment work offline?
Usually no, because a payment needs live confirmation. Say so plainly with a message such as Connect to the internet to pay.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.