A Quiet but Important Shift in How Software Can Work
Most software we use today is cloud-first: your data lives on someone else's servers, your access depends on an internet connection and a continuing subscription, and your ability to use your own files is governed by a third party's uptime and business decisions. Local-first software proposes a different model — one where your data lives on your device first, and sync is an enhancement rather than a requirement.
What Local-First Actually Means
The term was popularized by a research paper from Ink & Switch that outlined seven ideals for local-first software. In practical terms, local-first means:
- Your data is on your device. The authoritative copy lives locally, not on a remote server.
- It works offline. Full functionality is available without an internet connection.
- Collaboration is still possible. Sync between devices and users happens, but as a feature layered on top, not a prerequisite.
- You own your data long-term. If the company behind the software disappears, your files remain accessible and portable.
Why This Matters More Than It Used to
A few years ago, the trade-offs of cloud-first software felt worth it: ubiquitous access, easy collaboration, automatic backups. But several trends have sharpened the downsides:
- The wave of subscription price increases across major software platforms
- High-profile service shutdowns leaving users locked out of their own data
- Growing awareness of how personal data is used by cloud services
- Internet connectivity that still isn't reliable everywhere, or in every situation
Local-first design is a response to all of these concerns simultaneously.
Examples Worth Knowing About
A growing number of tools are exploring local-first architecture:
| Tool | Category | Local-First Aspect |
|---|---|---|
| Obsidian | Notes | Files stored as plain Markdown on device |
| Logseq | Notes / Knowledge | Local files, optional sync |
| Replit (desktop) | Development | Local-first mode for offline work |
| SQLite | Database | File-based, no server required |
| Zed | Code Editor | Fast, local-first with optional collaboration |
The Technical Challenge: Sync and Conflict Resolution
The hardest problem in local-first software is sync — specifically, what happens when two devices make conflicting changes while offline. CRDTs (Conflict-free Replicated Data Types) are the most promising technical approach, allowing changes from different devices to be merged automatically without data loss. This is an active area of research and engineering, and it's one reason local-first software has taken time to mature.
What It Means for How We Choose Tools
When evaluating software — especially tools for long-term use — it's worth asking: where does my data actually live? Can I use this offline? What happens to my files if the service shuts down? These questions aren't paranoia; they're reasonable criteria for tools you depend on. Local-first software often performs better on all three.
A Direction Worth Watching
Local-first isn't a rejection of the cloud — it's a rebalancing. The best local-first tools offer the convenience of sync and collaboration while keeping you in control of your data. As the ecosystem matures, this model is likely to become increasingly mainstream, and it deserves more attention than it currently gets.