Engineering

Offline-First Apps for Indian Field Teams

Why field apps in India must work without a network, what conflict resolution really means, and the four decisions that make or break an offline build.

Offline-First Apps for Indian Field Teams

In a warehouse basement, a rural beat or a lift lobby, the network is not there. If your field app needs it, your field team stops working. Offline-first is not a feature for them — it is the product.

Four decisions that decide everything

The sync queue

Every action becomes an entry in a local queue with a client-generated id. When the network returns, the queue drains in order, and the server treats repeats as the same action. Without those ids, a flaky connection creates duplicate orders — the single most common bug in Indian field apps.

SituationWhat the user should see
No network, order placedSaved · will sync — with a count of pending items
Sync failedA clear reason and a retry, not a silent failure
Conflict on a recordWhich version won, and a way to see the other
Stale stock data“As of 9:15 am”, not a number pretending to be live

What we build

React Native with a local database and an explicit sync queue, conflict rules agreed per field before development, and a pending-items indicator that is always visible. Tested with the network switched off, not just on wifi.

Questions

Does offline-first cost much more?

It adds meaningful work — typically a third to a half more than the same app online-only. For a field team it repays quickly in orders that do not get lost.

Field app offline kaam karega?

Haan — data phone par store hota hai, aur network aane par queue apne aap sync ho jaati hai. Duplicate orders na banein, iske liye har action ka apna id hota hai.

Read next