DEV Community

Vigor Guy
Vigor Guy

Posted on

Your notes should live on your device first

Disclosure: I built a notes app, and this article explains an idea behind it. The product is mentioned once, at the end.

Most note-taking apps ask you to trust a server before you have written a single word. You create an account, your notes upload to someone else's computer, and from then on your own thoughts are a guest in a system you do not control. It works fine — until the service changes its pricing, shuts down, has an outage, or gets breached. Then you find out how little of your own archive you actually owned.

Local-first means the opposite order: your notes live on your device first, and the cloud is an optional extra. The app saves to your own storage the moment you type. The network is never on the critical path. That one design choice changes almost everything about how the tool behaves.

Speed is a side effect of ownership

When a note is stored locally, opening it is a disk read, not a round trip. There is no spinner while a server decides whether you may see your own words. Cold boot drops under a second because there is nothing to fetch, no session to validate, no feed to load. The app feels instant because it is not waiting on anyone.

This is the same reason a paper notebook opens instantly. The tool is yours, it is already there, and it does not need permission to work. A notes app that has to phone home before it shows you your shopping list has the architecture backwards.

Offline is not a feature, it is a test

Every app claims to work offline. The honest test is simple: turn on airplane mode, close the app completely, reopen it, and try to write, search and edit. If anything hesitates, the app was never really offline — it was tolerating the network's absence.

A local-first app passes this test without thinking about it, because offline is its normal state. The network only matters for the things you explicitly choose to sync, and those can wait until you are back online. Your notes are never held hostage by a dead zone, a hotel Wi-Fi login page, or a server outage on the other side of the world.

Export is the only promise that matters

Every cloud notes service promises you can export your data. Read the fine print: exports are often partial, in a proprietary format, or buried three menus deep. A service that makes leaving hard is telling you something about its business model.

With local-first storage, there is nothing to export. The notes are already files on your device, in an open format you can read with any editor. Markdown is the obvious choice: plain text, human-readable in fifty years, convertible to anything. If an app cannot show you your notes as plain files, you do not own them — you rent access to them.

Sync should be a choice, not a condition

None of this means sync is bad. Having your notes on your phone and your laptop is genuinely useful. The point is that sync should be something you turn on because you want it, not something the app requires before it lets you write.

The right order is: write first, save locally, sync when you choose. If sync breaks, you lose convenience, not your notes. If a server disappears, you lose a copy, not the original. That is the difference between a tool you use and a service you depend on.

Privacy follows from architecture

A server cannot leak, sell or be compelled to hand over notes it never received. That is not a policy promise, it is a property of where the data lives. Privacy policies can change; architecture is harder to quietly rewrite.

This is why encryption matters most at the edges: notes that do leave your device — a shared link, a sync copy, a backup — should be encrypted before they travel. But the notes that never leave need no trust at all. They are simply yours, on a device you control, behind a lock screen you chose.

The test that matters

Before you commit your thinking to any notes app, try this: write a note, close the app, disconnect from the internet, reopen it, and search for what you wrote. If it works, the app respects you. If it asks you to sign in first, it does not — however good its features look online.

Then ask one more question: where is the file? If the answer is a folder you can open, back up and read without the app, you have found a tool worth keeping. If the answer is a database on someone else's server, you have found a landlord, not a notebook.

I built Outsmart Notes around this idea: your notes live on your device first, in plain markdown, with sync as an option rather than a requirement. You can try it at https://outsmartnotes.com

Top comments (0)