What offline-first really means
Designing for the power cut, not around it. Most health software treats connectivity as normal and outages as exceptions. In much of Africa that assumption is backwards.
The assumption underneath the software
Nearly every clinical system on the market was designed somewhere with reliable mains power and constant broadband. That assumption is not written in the documentation, but it is baked into the architecture: the client talks to the server, and if it cannot, it waits.
Deploy that in a facility where power fails several times a week and the network is intermittent, and the software does not merely slow down. It stops being usable at exactly the moments the facility is under most strain.
A system that only works when conditions are good is not a system. It is a demonstration.
Three levels of "offline"
The word is used loosely, so it is worth separating what vendors mean by it.
Read-only caching. The system holds a copy of recent records so staff can look things up during an outage, but nothing new can be entered. Useful, but it stops the facility working.
Queued writes. New entries are held locally and sent when the connection returns. Better, but it raises the hard question: what happens when two sites edited the same record while apart?
True local-first operation. The facility runs fully on local capture, with a defined reconciliation model for conflicts, and synchronisation as a background process rather than a precondition. This is the only version that survives a bad week.
The unglamorous part: conflict
Reconciliation is where offline-first systems are actually won or lost. If a nurse records observations at the bedside while the pharmacy updates the same patient's medication from a disconnected terminal, both are correct and both must survive.
The engineering answer is to treat clinical events as append-only facts with timestamps and authorship, rather than as fields to be overwritten. You do not merge two versions of a record. You keep both events and let the record show the sequence.
Why it is a commercial argument, not just a technical one
Global vendors can match most feature lists. What they cannot easily claim is that they were designed for a facility where power is a variable. That is not a marketing position. It is a set of architectural decisions taken early and paid for in complexity.
An engineering note from the Genesys team on how we build for African infrastructure conditions.