Local-first software in 2026 - why it is back, and what it actually means

For most of the 2010s, the direction of software was obvious: everything moves to the cloud. Notes, documents, tasks, photos. Your data lived on someone else’s server, and the app on your device was a window onto it.

In the last few years, the pendulum has swung back noticeably. “Local-first” appears in product pages, developer conferences and app store descriptions. Here is what it means, why it is resonating now, and where it falls short.

What local-first means

The term comes from a 2019 essay by Ink & Switch, Local-first software: you own your data, in spite of the cloud. It sets out ideals, including:

• Fast: no waiting on a server for ordinary actions.
• Works offline.
• Your data is on your device as the primary copy.
• Longevity: data stays usable even if the company disappears.
• Privacy and security by default.
• User control over the data.
• Multi-device and collaboration, where needed, built on top rather than as a requirement.

Local-first does not mean “no cloud ever”. It means the cloud is optional, not the foundation.

Why it is resonating now

• AI changed the privacy question. People now ask what happens to their text when it goes to a service, because so many services use it for AI features.
• Shutdowns and price changes taught people that cloud apps can disappear or double in price.
• Subscriptions piled up. See subscription fatigue in productivity apps.
• Better tools for developers. Sync engines and CRDT libraries make local-first collaboration more practical than it was.
• Hardware got fast. A laptop can run search over years of notes, or a small AI model, without a server.

The honest trade-offs

• Sync is hard. Getting data across devices reliably, with conflicts, is genuinely difficult. Cloud apps make it look easy because the server is the single source of truth.
• Backups become your responsibility, at least partly.
• Collaboration is harder than in a cloud-native document.
• Uninstalling can lose data if the app keeps it in its own storage, as Microsoft Store apps do.

How Jot applies it

Jot is a local-first capture tool:

• Every capture goes into one SQLite database on your PC, written in WAL mode so a crash does not lose an acknowledged capture. See nothing on the save path waits.
• No account is needed for capture, parsing, reminders or search.
• The webview cannot make network calls at all; anything networked goes through one Rust-side seam. See the webview that cannot phone home.
• Daily local backups and a Markdown export mean your data is readable without Jot.
• Optional features that need a network - bring-your-own-key AI, seven-day encrypted web copies, and task sync on the roadmap - are off until you use them.

How to judge a “local-first” claim

Ask four questions:

1. Can I use it fully offline?
2. Where is the primary copy of my data?
3. Can I export it in a readable format?
4. If the company disappeared tomorrow, could I still open my data?

If the answers are yes, on my device, yes, and yes, it is local-first in the sense that matters.

Jot is on the Microsoft Store.

Jot is a quick-capture app for Windows: one hotkey, one line, back to what you were doing. What it is, or what is still unproven.