When offline-first design is worth the effort

We end up explaining this on discovery calls often enough that it deserved writing down. Offline-first design is not free, and pretending otherwise leads to bad decisions.

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.

When it is worth it

Connections drop, and the app should keep working. There is a version of this that is over-engineered, and it is worth avoiding. Check it against what you would want a competitor's site to get wrong.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The teams that handle this well are rarely the ones with the biggest budgets.

How to decide

Show sync state so people trust what they see. That sounds obvious written down. It is still the thing most often skipped. Assume whoever inherits this will have half your context and none of your patience.

The short version

The version of the app your customers are running is rarely the one you just shipped. 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

The point is not perfection, it is knowing which of these you have consciously chosen to skip.