Back to all posts
Offline & Sync7 min read·October 25, 2026

How Should Your App Work Without an Internet Connection?

TB
ThynkBlox Apps Team
App Engineering

To plan offline mode for a mobile app, decide which tasks users must be able to finish without a connection, then define what happens to their data. For each task, choose whether the app shows a saved copy, keeps an edit waiting to send, or requires an online check. Choose a sync approach after those decisions, with clear rules for outdated information, conflicting edits and reconnection.

Which tasks should remain available offline?

Start with a situation: a user opens your app somewhere with no reliable connection. What do they need to accomplish before they can move on?

For a visit-recording app, that might mean reading an assigned checklist, adding notes and saving a draft report. Assigning work to another person could wait.

Write the offline promise into your app MVP scope. Make it specific enough to test.

Show the right state while data loads, is missing or fails: see designing loading, empty and error states.

User taskSuggested offline behaviourWhat the user should see
Read an already downloaded checklistShow the saved copyWhen it was last updated
Open a checklist never downloadedExplain that it is unavailableA clear instruction to connect
Add visit notesSave on the device and queue the edit“Saved on this device. Waiting to sync.”
Attach a photoKeep it locally until uploadedA separate upload status
Assign work to someone elseRequire an online checkWhy a connection is needed
Submit a final reportFollow the agreed submission ruleA distinction between pending and accepted

Treat this as a product decision, not a promise that every feature works everywhere.

What should users be able to read from a saved copy?

Cached reads mean showing information previously stored on the device. Decide what to save, how users obtain it and how they know it is ready.

For each screen, specify:

  • Which records and attachments are included.
  • Whether saving happens automatically or through a download action.
  • Whether users can check offline readiness before leaving.
  • What appears when only part of the content is available.
  • When saved content should be refreshed or removed.

Avoid making an unopened screen look empty when its contents simply have not been downloaded. Use a message such as “This checklist is not available offline yet.”

Keep sensitive information in the discussion too. Decide whether it belongs on the device, who should be able to open it and what signing out should do to saved copies.

Which edits should wait to sync?

Queued edits are changes saved on the device for sending later. Define a clear lifecycle: saved locally, waiting, sending, accepted, or needing attention. For a worked example in a stock-counting app, see stock counting app features for retail shops.

Use those states consistently. “Saved” should not leave users guessing whether another person can see their work.

Specify whether users can edit or cancel a pending change. For related actions, define their order: a report should not appear complete while required attachments are still waiting.

Keep a queued change until the app receives confirmation that it was accepted. If delivery is uncertain, show that uncertainty and provide a safe retry path.

Make repeated attempts part of the design: retrying the same submission should not create another report. See how to prevent duplicate submissions in a mobile app.

How should you resolve conflicting edits?

A conflict needs a rule whenever a queued change meets information that has changed elsewhere.

Imagine an illustrative visit report. Someone edits its access instructions offline while another person updates the shared instructions online. On reconnection, which version should remain?

Choose by the meaning of the field, rather than applying one rule everywhere.

Type of changeSuggested rule
A new noteAdd it as a separate entry
Changes to unrelated fieldsCombine them where product rules allow
Two edits to the same instructionShow both and request a choice
An edit to a deleted recordPreserve the draft and explain the deletion
A request for a limited place or itemRequire online acceptance before confirming

Avoid silently replacing meaningful work with whichever edit arrives last. If automatic replacement is acceptable for a minor preference, document that exception.

When asking users to choose, show readable values and explain the consequence. Offer a way to preserve their draft before discarding it.

How should the app label stale data?

Separate connection status from information freshness. A connected app should still explain when a displayed record has not been refreshed.

Choose labels that answer the user's immediate question:

  • “Showing a saved copy.”
  • “Last updated before your current session.”
  • “Your changes are waiting to sync.”
  • “Could not refresh. Your saved copy is still available.”

Where useful, show the actual last successful update time. Do not change it merely because the app attempted a refresh.

Set freshness rules for decisions that need current information. A saved checklist might remain useful, while confirming availability might require an online check.

Place the label beside the affected information. A general offline banner should not carry the whole explanation for records with different update states.

What should happen when the connection returns?

Plan reconnection as a visible sequence, with a result for each pending action.

First, show that the app is trying to reconnect. Then check access, send eligible changes in the required order and handle any conflicts. Refresh shared information and show what was accepted, what remains pending and what needs attention.

Do not show “Everything synced” while an attachment is still uploading or a change has been rejected.

Keep the user's current work stable during this process. Avoid replacing text while they are typing or moving them to another screen without explanation.

If access has expired, preserve pending work and explain the next step: “Sign in again to send your saved changes.” After sign-in, check permissions before attempting delivery. A restored connection should not count as permission to apply every queued action.

What would a complete offline journey look like?

Consider this illustrative plan for a visit-recording app:

  1. Before travelling, the user downloads the assigned checklist and sees confirmation that its questions and reference images are ready.
  2. Without a connection, the user opens it, adds notes and attaches a photo.
  3. The report shows “Saved on this device. Waiting to sync.”
  4. The user closes and reopens the app. The draft and pending status remain available.
  5. After reconnection, the app sends the report and then the photo.
  6. If either needs attention, the app identifies the item and preserves the user's work.
  7. Only after both are accepted does the report show “Synced.”

Add the interruption cases to your acceptance checklist: close the app during delivery, lose the connection again, encounter changed permissions and retry an uncertain submission.

Use the same journey in testing before release, checking the final shared record as well as the phone's status message.

Which common mistakes should you avoid?

Choosing the sync tool before the offline tasks. Define the behaviour first, then assess whether a tool supports it. For sync that runs after the user leaves the app, see Android background tasks and sync.

Treating a local save as a completed submission. Distinguish work stored on the phone from work accepted for sharing.

Making failure look like success. Keep rejected changes visible and explain how to resolve them.

Offering a download button without a readiness check. Show whether required records and attachments are actually available.

Forgetting account changes. Decide what happens to pending work when someone signs out or switches accounts. Do not send one account's drafts under another account.

When should a task require a connection?

Require a connection when the task needs current shared information or immediate authorisation under your product rules.

You can still let users prepare a draft offline. For example, let them complete a request, but label it as pending until accepted. Explain this boundary before they spend time entering information.

Offline mode does not need to cover every action. A narrow, dependable promise is a useful starting point.

What are the frequently asked questions?

Does offline mode need to be in the first release?

Include it when a core task must work without reliable connectivity. Otherwise, define clear connection errors and preserve unfinished input, then assess broader offline support against real user needs.

Should syncing happen automatically?

Use automatic syncing where the result is safe and predictable. Show progress and exceptions. For actions requiring review, let users confirm before sending.

Can users work offline on several devices?

Decide this explicitly. Specify how each device obtains records, how pending work is identified and how competing edits are resolved. Show local pending work separately from shared accepted changes.

What should you give your development team?

Provide the task table, saved-data rules, edit states, conflict decisions, status wording and reconnection checklist. Together, these define an offline experience that can be built and verified. For one common case, see how to make photo uploads reliable in a mobile app.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.