← All insights

Insight / Web and apps

Published

Will downloaded apps work offline? Design for the moments when they cannot connect

A downloaded app may still depend on a server. Compare offline models and learn how local data, visible sync states, retries and recovery keep essential work moving.

Hand holding a smartphone with a blank screen
Photo: Jakub Żerdzicki / Unsplash

Downloading an app gives a device the software needed to launch it. It does not necessarily download the information, permissions or services the app needs to finish a task. A store app can depend on an API for every action; a web app can keep useful content on the device. The right question is: which tasks must remain possible when the connection disappears?

That may happen in a lift, on a train, at a worksite or when a server is unavailable. Slow and unstable connections also matter: a request can time out after the person has pressed Submit, leaving them unsure whether it succeeded. Android’s offline-first guidance starts with the critical tasks and data sources, rather than assuming that installing an app makes them available.

Four workable models

Online only. The interface may open without a connection, but live search, payment, account checks or saving changes require a server. This can be the right choice for actions that need immediate confirmation. Say so before the user starts and provide a useful failure message if a request cannot complete.

Offline reading. Previously saved documents, schedules or product details can be viewed without a network. The interface should show when information was last updated, especially when a stale instruction could cause harm or wasted work.

Offline editing with later sync. A person can fill in a field report or update a task locally. The app saves the change on the device and sends it when it can connect. This requires more than a cache: it needs a durable local record, a queue, server rules and a way to resolve conflicting edits.

Fully local. The core task uses data and logic already on the device and may never need a server. It can still have optional backup or updates. “Local” should be tested literally: first launch, restart, storage full and a long period without access.

Treat reconnection as a process, not a magic moment

For important offline edits, save locally first, then mark them as waiting to sync. Retry failed requests with spacing between attempts so a struggling service is not flooded. Give each operation a stable identifier and make the server treat retries with that identifier as the same operation, avoiding duplicate orders or reports. The server should confirm receipt before the interface says synced. If two devices change the same record while disconnected, the team needs a conflict rule and, where necessary, a way for a person to choose which version to keep. Android’s guide describes queued and local-first writes, conflict resolution and retry work.

Do not rely on a connectivity badge as proof that the server can be reached. The web’s navigator.onLine indicator is inherently unreliable; a device can appear connected while its request fails. Web Background Sync can help on supported browsers, but availability is limited and browsers restrict retries. Native platforms also schedule background work under their own conditions. Keep pending work visible and retry when the app is open, as well as using supported background mechanisms.

Make failure and recovery part of the interface

Use separate, plain states: saved on this device, waiting to sync, confirmed by the server and needs your attention. Keep the person’s input when authentication expires or a response is uncertain. For high-stakes actions, such as a payment, do not label an unconfirmed attempt as complete; provide a safe way to check its outcome before trying again.

For web apps, local storage also has limits. IndexedDB can hold offline data, but browser-managed storage is best-effort by default and can be cleared or evicted. Test low-storage devices, browser data clearing and unsent changes. The promise to make is specific: these tasks work offline; these changes are kept here until the service confirms them. Then verify that promise through disconnection, reconnection and failed-sync tests.

External project website

Open this project site?

is hosted at . It will open in a new tab.