Interactive graph
Local-first Software
Table of Contents
Local-first means the device holds the truth; sync is optional icing - backup should behave the same way.
Key Concept
- Truth lives on the device first; cloud sync is backup, not the vault.
- Choose what is public, what stays private, and what gets encrypted before it leaves the room.
- Sync should merge edits without picking last-write-wins by clock alone.
Level 1 - Recognize
Local-first software keeps the master copy on your device and treats cloud sync as backup, not the vault.
Level 2 - Explain
Like keeping your diary in your room and photocopying it for safety, your phone or computer owns the real file first.
Level 3 - Use
Pick tools that work offline with full features - sync is insurance, not the place you crawl to after an outage.
Level 4 - Connect
If the service vanishes, your notes survive on the device - cloud-only stacks fail when the tenant changes the rules or the network drops.
Level 5 - Create
Extend local-first into Building a Personal API and Digital Minimalism - read and write without begging a server.
Examples
- If the phone dies mid-grocery run, the list on the fridge still works.
- Grandma's recipe cards live in the kitchen drawer - not an app that might vanish.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Building a Personal API | Local files vs push API when boring export wins |
| contradicts | Drafting in Public | when private-first truth beats publishing before I am ready |
| extends | PKM | Your device holds the truth and sync is icing - that is how a brain backup should behave |
