Why we ship offline-first or we do not ship at all
Connectivity is not a personality test. A real system has to keep its promise when the signal disappears.
The network is part of the environment.
The cleanest product demo assumes a stable connection. Real work happens in rooms, basements, back offices and streets where the network is variable, shared or simply absent.
If the system treats disconnection as an exceptional error, the operator becomes responsible for recovering from conditions they did not create.
Local-first changes the shape of trust.
The user should be able to continue the task, see that the work is safe and understand what will happen when the connection returns. That requires local state, a clear queue and reconciliation designed as part of the product.
It also changes the interface: status must be honest without becoming a warning every time the world is imperfect.
The lesson was continuity.
Offline-first is not about pretending a network does not matter. It is about making the system resilient to the world as it is.
When the connection comes back, the best experience is not a dramatic recovery. It is that the work simply continues.