System Type: Edge & Offline-First

Patterns, failure modes, and anti-patterns for systems that operate under intermittent connectivity and constrained resources.

1. Offline-First Architecture

The fundamental assumption shift: the network is not a dependency — it is an optimization. An offline-first system is fully functional without connectivity and becomes better when connectivity is available. This is the opposite of how most systems are built, where the server is the source of truth and the client is a thin rendering layer that breaks the moment the network disappears.

The Offline Spectrum

Most teams think they're building "offline-tolerant" but their users need "offline-first." The gap between those two is enormous — it's the difference between showing a spinner with "waiting for connection" and letting the user do their entire job on an airplane.

Local-First as a Design Principle

Local-first means the device has a complete, usable copy of the data the user needs. Not a cache — a replica. The distinction matters:

• Cache: Server is authoritative. Cache is disposable. Stale cache means stale UI. Cache miss means broken feature.
• Replica: Device has a full copy. Local writes are first-class, not optimistic guesses. The device can operate indefinitely without the server. Sync is reconciliation between peers, not cache invalidation.

Design consequences of treating the device as a replica:

• The data model must be defined in terms of local operations, not server API calls.
• Every write must succeed locally before any network interaction.
• The UI must never show a loading state for data the user has already seen.
• Conflict resolution is a first-class design concern, not an edge case handler.

Client-Side Storage

…