Offline-first design for small teams

The version of this that works is simpler than the version most people imagine. Most advice about offline-first design assumes a team that does not exist at your size. Here is the version that does not.

Mobile releases are slower to correct than web ones, so the cost of shipping a mistake is higher. If it only works because one person remembers to do something, it does not work yet.

What to keep

Connections drop, and the app should keep working. The teams that handle this well are rarely the ones with the biggest budgets. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. In practice this is a scheduling problem more than a technical one.

How we handle it

Show sync state so people trust what they see. None of that requires a large budget, only a decision and someone to own it. Assume whoever inherits this will have half your context and none of your patience.

The short version

You do not control the device, the network, or the operating system version, and the design has to accept that. Three things worth confirming about offline-first design before you move on:

• Someone can say what the current setup is without going to look
• Conflict resolution is the part teams forget to design — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.