Why we build offline-first, and why it matters in India

A pitch deck says "cloud". A factory in an industrial estate outside a tier-two city says something else: the link drops for twenty minutes most afternoons, and it goes entirely during the monsoon.

Software that stops working when the link drops is not a small inconvenience in that setting. It stops production, or it stops a queue at a school gate, or it stops a hospital from discharging a patient.

What offline-first actually means

It does not mean "works offline for a bit". It means the local system is the source of truth for the operation in front of it, and the cloud is a synchronisation target.

In practice:

• The application and the database run on a server in the building. Everything works on the LAN with no internet at all.
• RFID readers buffer their reads locally and forward them when the network returns. A reader with no network still records everything.
• Android handhelds hold their work list and their reads on the device and sync when they come back into range.
• Where cloud is used, sync is one-way-safe: conflicting edits are resolved with a rule, not by whichever save happened last.

The cost of doing this

It is more work. Two data paths have to be correct instead of one, and conflict handling has to be thought through rather than assumed away. That is why a lot of software does not do it.

The cost of not doing this

We have seen a school gate with cloud-only attendance that failed on the first day of monsoon and had 1,800 students queuing while a teacher wrote names on paper. We have seen a warehouse that could not dispatch because the WMS was hosted in another country and the leased line was down.

When cloud-only is fine

Plenty of the time. An office system used by twenty people with reliable fibre does not need this. A marketing website does not need it. Our own AIR product is cloud-only by design, because it is aimed at businesses that want to start in days without a server.

The point is that it should be a decision, made against the actual site conditions, rather than a default that nobody questioned until the day it mattered.