Field connectivity: managing offline mode and dead zones in logistics

Field connectivity: an underestimated challenge

When designing a driver app, connectivity is often treated as a given: the driver has a data plan, the network is available, data flows. The field reality is more nuanced. A motorway tunnel, an industrial estate in a steep valley, an underground refrigerated warehouse, or simply a rural dead zone — any of these contexts can temporarily cut the driver off from the network, sometimes at the precise moment they need to consult a delivery note or record a signature.

An app that only works when connected is a fragile app. Operational robustness requires treating offline not as an exception, but as a normal state that the system must handle gracefully.

PWA and Service Worker: cache in the service of resilience

Progressive Web Apps (PWA) have integrated offline as a first-class feature through Service Workers. A Service Worker is a script that runs in the background in the browser, independently of the web page. It intercepts network requests and can redirect them to a local cache when the connection is absent.

In a well-designed driver app, the Service Worker caches on first connection:

• The static resources of the application (HTML, CSS, JavaScript, icons)
• The data for the current route (list of stops, addresses, delivery instructions)
• The forms and delivery notes associated with the day

When the network disappears, the Service Worker serves this data from the cache. The driver continues navigating their route, consulting delivery information, and filling in forms — without noticing the network interruption.

The sync queue: losing nothing offline

Cache solves offline reading. A separate mechanism is needed for writes: recording a signature, marking a parcel as delivered, logging an incident. These actions cannot simply wait — they must be made reliable.

The solution is called a sync queue (or outbox):

• Every driver action (signature, confirmation, photo) is first stored locally in the device's embedded database (IndexedDB in a browser).
• A local indicator immediately confirms to the driver that their action has been registered, even without a network.
• When the connection is restored, the sync queue automatically sends pending events to the server in chronological order.
• In the event of a conflict (another user has modified the same delivery), a conflict-resolution logic determines which version prevails.

The result: zero data loss, even if the driver crosses several consecutive dead zones on a single route.

IndexedDB and localStorage: storing locally on the device

• localStorage: simple key-value storage, synchronous, suited to lightweight preferences and authentication tokens. Limited in volume and unstructured.
• IndexedDB: embedded database, asynchronous, structured as objects. Suited to large or complex data — route lists, forms, delivery history.

A robust driver app uses IndexedDB for business route data and localStorage for session data. The combination enables fully autonomous operation on the device, with no network dependency.

Managing network transitions smoothly

Offline management is not limited to fully disconnected areas. Transitions are often gradual: weak signal, lost packets, high latency. A well-designed app handles these intermediate states:

• It detects network quality and adapts its behaviour (no high-resolution map loading on a weak signal).
• It displays a discreet connection status indicator without blocking the driver.
• It prioritises critical data (next stops, delivery instructions) in its sync requests, before secondary data (history, statistics).

dropfleet and offline resilience

The dropfleet driver app is designed as an offline-first PWA. The route is loaded in full at the start of the session and cached locally. Driver actions — confirmations, signatures, incidents — are stored in a queue and synchronised with the platform as soon as the network is available. The dispatcher always has an up-to-date view, delayed only by transit time through areas without network.

A driver app that works even without a network? Try dropfleet free for 14 days — no credit card, ready in 5 minutes.