Local-First
Software design where data lives primarily on your devices, with cloud as optional sync.
Also known as: Local-first software, Offline-first, Device-centric
Category: Concepts
Tags: technologies, software-design, privacy, independence, architecture
Explanation
Local-first is a software design philosophy where your data lives primarily on your own devices, with cloud services used for sync and backup rather than as the primary data store. This contrasts with cloud-first (data lives on servers, accessed via internet). Local-first principles: data is yours (stored on your devices), works offline (no internet required for core functions), syncs across devices (when connected), fast (no network latency for local operations), and long-term accessible (not dependent on service survival). Benefits include: privacy (data stays on your devices), reliability (works without internet), performance (no network round-trips), longevity (survives service shutdowns), and ownership (truly your data). Challenges: sync is hard (conflict resolution, consistency), backup responsibility shifts to user, collaboration requires more complexity, and some features genuinely need servers. Technologies enabling local-first: CRDTs (Conflict-free Replicated Data Types), local databases (SQLite, IndexedDB), peer-to-peer protocols, and sync engines. Examples: Obsidian (notes), Git (code), and some newer apps built on local-first principles. For knowledge workers, local-first provides: true data ownership, offline capability, and independence from service continuity.
Related Concepts
← Back to all concepts