Local-first is a set of properties
Local-first software aims to make the user's own device a primary place for data and interaction. It should work well without continuous network access, allow the user to retain meaningful control over their data, and synchronize when connections are available. The term is not equivalent to “never use a server.”
Offline capability, portability, privacy, collaboration, and durability can reinforce one another, but they also create trade-offs. A local copy needs backups. Multi-device editing needs conflict handling. End-to-end encryption can protect content in transit and on servers while complicating search and recovery.
Ask practical questions
Before adopting a tool, test a short list:
- Can I create and edit a note while disconnected?
- Can I export the source without losing essential content?
- What happens if two devices edit the same note?
- Can I restore the archive without the original vendor?
- Who can access the stored content and encryption keys?
The answers should be tested, not inferred from a marketing label. A plain-text application may still depend on a proprietary sync backend, while a more complex tool may offer strong export and recovery mechanisms.
Conflicts are part of synchronization
A replicated document may change independently on two devices. “Last write wins” is simple but can silently discard meaningful edits. Conflict-free replicated data types (CRDTs) and operational transformation (OT) are approaches to collaborative editing, each with implementation details and trade-offs.
For a personal archive, an explicit conflict file can sometimes be safer than aggressive automatic merging. Preserve both versions, review differences, and record the chosen result when the meaning matters.
Design an offline experiment
A useful evaluation requires no benchmark claims. Disconnect a device, create two notes, edit one that already exists, reconnect, and inspect synchronization. Then edit the same note on two disconnected devices and see what happens after reconnection. Record what the system does; do not extrapolate from a single successful sync to guaranteed correctness.
Test backup separately. Restore into a clean directory and open the data with a basic tool. If you cannot explain the restore process, the system does not yet provide durable ownership.
Privacy depends on the whole path
Storage encryption is valuable, but metadata, access patterns, backups, and connected services may still reveal information. Review the actual threat model. For an ordinary personal notebook, reliable backups and good account security may be more immediately important than exotic cryptography.
Notebook principle: offline usability, recoverability, and understandable ownership are product features—not implementation details.