Local-first software, explained

Most software you use today works the other way around: your data lives on a server, and your device is a thin window into it. Open the app with no internet connection and it either refuses to work or shows you a stale cache. Close your account and your data is gone. The company shuts down and everything you built in the app disappears. This is the cloud-first model, and it is so common that most people have stopped noticing its costs.

Local-first software takes a different position: your data belongs on your device first. The cloud is a useful supplement for sync and backup, not the authoritative source of truth.

What local-first means in practice

The core principle is simple: the app works fully without an internet connection. All reads and writes go to local storage — a database or file system on your device — and the app does not need to phone home to do its job.

This is not the same as "offline mode" in a cloud app, which typically means a degraded experience with a spinner that goes away when you reconnect. A local-first app is designed from the start with your device as the primary location, so offline is not a special case — it is the default.

Sync, when it exists, is an optional layer on top. Your local data is the truth; the server is a place to mirror it so you can access it from multiple devices or recover it after a device failure.

Why it matters

Ownership. If your data is on your device, you own it in a real and practical sense. You can copy it, back it up, open it in other tools, or take it somewhere else — without asking anyone's permission. Cloud-first apps often make this technically possible but operationally difficult, because the data they export is not always in a format other tools can use.

Availability. Software that works offline works on planes, in basements, in rural areas, and in any other place where connectivity is unreliable. It also works when a third-party service has an outage, when rate limits kick in, or when the company is simply having a bad day. Your work does not stop because someone else's server does.

Longevity. Cloud apps depend on the company that runs them staying in business, keeping the service up, and choosing not to change the pricing or terms in ways that affect you. Local-first apps can outlive their creators. If the developer stops maintaining OriginText tomorrow, every note you have written is still on your device, in standard markdown files, readable by any text editor on earth.

Privacy. When data lives on your device, it is much harder for third parties — the company, hackers who breach the company, governments who subpoena the company — to access it. The surface area of risk is your device, not a shared server full of everyone's data.

The tradeoff

Local-first is not free. Sync across devices is harder to implement correctly than a server-side database. Collaboration features — multiple people editing the same document simultaneously — require sophisticated conflict resolution that most local-first apps do not yet provide. Backup is your responsibility unless the app provides an encrypted sync option.

These are real limitations. Local-first is the right model for personal tools where ownership and privacy matter more than real-time collaboration. For a shared team workspace where five people are editing the same document at once, a cloud-first architecture may make more sense.

How OriginText is built this way

OriginText stores everything in on-device storage — specifically the browser's Origin Private File System (OPFS) and IndexedDB — so notes are available immediately with no network request. The app is a Progressive Web App (PWA), which means it installs on your device, loads from a local cache, and keeps working when the connection drops.

Encryption is applied at rest, on your device, before anything optional is sent anywhere. If you turn on sync, your notes are encrypted locally before they leave your device, and only ciphertext crosses the network. The sync server never has your keys.

This combination — local storage, offline-capable PWA, and optional zero-knowledge encrypted sync — is what it means in practice for your notes to be local-first. The cloud is a convenience you can opt into, not a dependency you are locked into.