When people design software in Kathmandu, they design for Kathmandu's internet. Then the software goes to Kailali, or Kanchanpur, or a hill village three hours past the last tower, and the assumptions quietly fall apart. A form that needs a live connection to save is not a form in those places — it is a locked door.
We learned this early. During the Covid-19 lockdown of 2020, our founding team — then working as Promethean Technologies — was asked to move whole educational institutions in Nepal's far-west online in a matter of weeks. There was no option to wait for perfect connectivity; the work had to function in the conditions that actually existed on the ground.
Connectivity is a range, not a switch
“Has internet / has no internet” is the wrong mental model. In practice you get a spectrum: a strong connection at the district headquarters, a weak and intermittent one at the ward office, and nothing at all where a field worker is standing when they need to record something. A system that only works at the top of that range fails exactly where the real work happens.
Offline-first is an architecture, not a bolt-on
The instinct is to build an online system and later “add offline support.” It rarely works, because the hard parts — where data lives with no connection, what happens when two people edit the same record on two disconnected phones, how you reconcile it all when a signal appears — have to be designed in from the start. Offline-first means the device is the primary place data is captured, and sync is a background process that catches up when it can.
Sync is where the honesty is
Anyone can cache a form. The real test is conflict resolution: when the same record has been touched in two places, what is the truth? A serious offline system has a deliberate answer, not a silent overwrite. If a vendor can't explain their conflict-resolution approach in plain language, they haven't built for the field.
Build for the people, not just the network
The far-west taught us that the hardest constraint often isn't bandwidth — it's that the person entering data has never used a system like this before. Interfaces have to be forgiving, training has to leave people able to operate on their own, and the goal is always to hand over something the organisation can run itself.
Frequently asked
- What does offline-first actually mean?
- The device is the primary place data is captured and held, and synchronisation runs as a background process that catches up when connectivity returns — so the user never waits for the network to do their job.
- Why is conflict resolution important?
- When the same record is edited in two disconnected places, a serious offline system has a deliberate rule for which version wins — not a silent overwrite that loses someone's fieldwork.