General 26 min read

Why Your Notes Should Outlive Your App

MMNMNOTE
local-firstfile-over-appplain-textmarkdowndata-ownershiplock-inmanifestopkm
Updated September 23, 2026

Apps end. Files endure. The most important question to ask of any note-taking tool in 2026 is not how it makes you feel today, but whether your sentences will still open on a computer in 2046 — when the company is gone and the format is forgotten. The answer separates a notebook from a hostage situation.

The case for thinking this way is no longer theoretical. Evernote, founded in 2000, was once valued at a billion dollars; by July 2023, its new Italian owner had laid off nearly every US employee.1 Roam Research, briefly the darling of the personal knowledge management movement, now costs $15 a month and is sustained by a "Believer" cohort on a five-year prepay.2 Notion's "Plus" plan rose alongside an AI add-on bundled at $10 per user per month.3 None of these stories is a scandal. Each is the ordinary life cycle of a cloud product. The question is whether your thinking should ride along.

What most note-takers believe

Most note-takers believe a good app is the goal — pick the best tool, master it, organize a vault, and your second brain is built. The reasoning is reasonable enough. A note app sits on every screen they own; the friction of switching is real; and the marketing of every major app has trained them to identify with a platform, not a file format.

Steph Ango, the chief executive of Obsidian, calls this assumption out in a sentence that has been quoted across the open web: "In the fullness of time, the files you create are more important than the tools you use to create them. Apps are ephemeral, but your files have a chance to last."4 He is not the only person to make this argument. Derek Sivers, who has written four books and four hundred essays in plain text files since 1990, says it plainer: "Plain text will be there. Will Microsoft Word? Evernote? Notion? Maybe. Maybe not. But plain text? Always. Everywhere."5 Cal Newport's Slow Productivity, which has sold into the millions, makes the same case in the language of focus: own the artifact, not the chrome around it.6

The belief itself is not silly. The belief becomes dangerous only when the file format and the app are the same thing.

Why the conventional view fails

The conventional view fails because cloud apps are structurally allowed to fail you. In Martin Kleppmann's local-first paper — cited so often on Hacker News that the thread broke 700 points twice in five years — cloud software stores "the primary, authoritative copy of the data" on a server; the user's copy "is merely a cache."7 If the cache is all you control, the company controls the original.

That arrangement has produced a recurring pattern. Evernote, once the default note app for a generation, was acquired by Bending Spoons in November 2022; by July 2023 the buyer had fired "nearly every US employee" and relocated operations to Europe.1 Its personal plan rose from roughly $60 a year to $129.99 — a price hike that long-time subscribers in the official forum described as a "160% jump."8 Roam Research, the wiki-link product that briefly defined the PKM movement, still lists $15/month on its own pricing page and is sustained largely by users locked into a five-year Believer plan.2 Google Reader, the canonical case, went dark in July 2013 and taught a generation that "if I don't have a useable offline backup, I don't have data."9 Craft, beloved for its typography, stores notes in a proprietary JSON database; its own documentation concedes that "structuring items like pages, cards, and toggles can't be represented in linear editors, so they are flattened out."10 The export is lossy because the format is the product.

This is not malice. It is a pattern Cory Doctorow named in his January 2023 Wired essay: "Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves."11 He calls the pattern enshittification. It is the economic gravity of two-sided platforms. It applies to every app on the page.

The legal system has begun, at last, to notice. The European Union's Data Act entered into application on September 12, 2025, with a binding obligation on cloud providers to allow customers to switch services within a transitional period defined by the regulation and to phase out switching fees entirely by January 2027.12 IBM launched Sovereign Core on January 15, 2026, an "AI-ready sovereign-by-design" platform pitched explicitly at organizations that no longer trust their data to live anywhere a foreign vendor can reach it.13 When the world's largest enterprise vendors and the world's largest economic bloc both bet on data portability inside a single year, that is a signal. Your notes are downstream of that signal.

What works instead

The stricter test is set thirty years ahead. Ango again, this time on the math of durability: "If you want your writing to still be readable on a computer from the 2060s or 2160s, it's important that your notes can be read on a computer from the 1960s."4 A note tool passes this test if — and only if — the underlying file is plain, portable, and useful without the app.

Plain text passes that test. Markdown — the lightweight syntax John Gruber published on March 17, 2004 (with feedback from Aaron Swartz), with the stated goal of letting people "write using an easy-to-read and easy-to-write plain text format" — passes it twice.14 Two decades on, Markdown is the default text shape of GitHub, GitLab, Reddit, Stack Overflow, Discord, and most documentation pipelines.15 It is the closest thing the open web has to a universal note format. A Markdown file written today will open in a text editor, a code editor, an email client, an LLM prompt, a static site generator, and any future tool whose author has read a tutorial. It is the inheritance test in seven characters: a .md extension. (If the syntax is new to you, the Markdown cheat sheet covers the floor.)

The architecture beneath the file matters too. Kleppmann's local-first paper lays out seven ideals, in their exact wording: "No spinners: your work at your fingertips," "Your work is not trapped on one device," "The network is optional," "Seamless collaboration with your colleagues," "The Long Now," "Security and privacy by default," and "You retain ultimate ownership and control."7 The fifth ideal — "The Long Now," named after Brewster Kahle and Stewart Brand's long-now archival philosophy — is the one most note apps fail.16 An app that requires a server in Virginia to render a sentence you typed yesterday is not aimed at the Long Now. It is aimed at next quarter's renewal.

The local-first move is to invert the cache. Store the authoritative copy on the device. Treat the cloud as an optional courier. The file is the source of truth; sync is a convenience; the company that wrote the app is a contractor, not a landlord. Logseq, founded in 2020 by Tienson Qin, makes the same architectural bet at the open-source layer: "all data is stored locally on your device as plain text files… you are the complete owner of your data and can open the files in any text editor, even without Logseq."17 Obsidian makes the same bet at the commercial layer, which is why its founder can write the sentence about files outlasting apps without irony.4

Before and after

The clearest way to see the difference between a leased note and an owned one is to look at the same paragraph in two formats. The first lives inside a proprietary database and depends on a company. The second is a Markdown file you can open in any text editor written this century. The difference is structural, not aesthetic, and it changes everything about what you can do with the file tomorrow.

Before — in a typical cloud note app. The sentence lives inside a proprietary block tree. Pasting it elsewhere strips the formatting. Exporting it produces a brittle Markdown copy with broken internal links and missing media. The note depends on an account, a subscription, and an internet connection. If the company is acquired, repriced, or simply tired, the sentence is still on the server — but the way you reach it is not.

After — as a Markdown file. The same paragraph is a few hundred bytes of UTF-8, prefixed with a heading, peppered with [[wiki-links]], ended by a newline. It opens in Vim, in VS Code, in Marked, in GitHub, in a fresh browser tab, in a print-to-PDF dialog, in an email, in a future LLM that doesn't yet exist. The text is its own backup. The file is the contract. No company is required to read what you wrote.

That is the only practical asymmetry that matters. The first version of the paragraph is leased. The second is owned.

What to actually do tomorrow

The translation from manifesto to practice is short and concrete. There are five moves worth making this week, in order, each of which converts a piece of your existing note-taking workflow from leased to owned. None requires you to leave your current app on day one. The point is to make leaving possible at all.

  1. Pick a format, not an app. Choose Markdown or plain text. Both pass the 1960s-to-2160s test. Both render in every editor written this century. Stop evaluating note apps; start evaluating note formats.
  2. Move the authoritative copy off the cloud. Whether the storage is the device's filesystem, the browser's IndexedDB, or a folder you keep in Dropbox does not matter as much as this: the file exists where you can read it without an account.
  3. Test the export. Open the export of your current note app in a plain text editor. If headings, links, attachments, and structure survive without translation, the app is honest. If the export is a tar of HTML or a proprietary JSON dump, the file you thought you owned is a souvenir.
  4. Write the first sentence somewhere portable. Andy Matuschak's evergreen-note practice begins with a single observation: notes earn their durability by being atomic, plain, and revisable.18 Open a .md file. Type one sentence. The system is now older than any app you might choose to render it.
  5. Treat sync as a courier, not a custodian. End-to-end encryption, CRDT-based merge (the same Yjs and Automerge work Kleppmann has published since 2015), and offline-first apps make it possible to share notes without surrendering them.19 If sync requires you to upload the plaintext to a vendor's database, the vendor is the custodian. That is the model that produced Evernote.

None of this is moralism. It is hygiene. The notes that survive your apps will be the ones you can move without permission.

Who should not care about this

Honest balance is the cost of being cited. There are three kinds of readers for whom this entire argument is overhead: people whose notes are ephemeral by design, people locked into team collaboration tools by network effect, and power users whose existing app is already part of how they think. Each deserves a sentence.

If your notes are ephemeral by design — daily scratch, meeting reminders that age out in a week, a grocery list that doesn't survive Tuesday — a cloud notes app is a perfectly fine tool. The data is short-lived and the lock-in cost approaches zero. Apple Notes, Google Keep, Notion's free tier, and the system clipboard all do this job. They were built for it.

If you work inside a team whose collaboration tool is the network effect — a product manager whose specs live in Notion because every engineer is already there, a researcher whose lab uses a shared cloud workspace because the wiki search is the workflow — the cost of leaving is higher than the cost of staying, and the answer is the same answer most enterprises gave to email twenty-five years ago. Use the tool. Export quarterly. Do not pretend you are not renting.

And if you are a power user who has tuned a single proprietary app over years and produces work you are proud of inside it, this essay is not asking you to leave. It is asking you to keep one canonical plain-text copy somewhere the app cannot reach. The point is not to flee. The point is to make leaving possible.

The declaration

If files outlast apps, then the question to ask of a note tool is not how clever it is, but how easily your sentences leave it. A note app earns trust by being optional to its own files. The note tools that pass that test are the ones whose sentences will still open on a computer in 2046. The note tools that fail it will be remembered the way Google Reader is remembered — by the people who got out in time.

If your notes deserve to outlive your app, MNMNOTE (mnmnote.com) lives in your browser — markdown in, markdown out, no account, no install.

Frequently asked questions

What does "local-first" actually mean?

Local-first software, defined by Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, and Mark McGranaghan in their 2019 Onward! paper, is a class of software in which "the authoritative copy" of the data is on the user's device, not a server.7 Cloud sync is optional. Seven ideals follow, including "the network is optional" and "you retain ultimate ownership and control."

Is Markdown really enough to last fifty years?

Markdown was published by John Gruber on March 17, 2004 (with feedback from Aaron Swartz), designed to be readable as plain text without conversion.14 Its source is human-readable UTF-8. CommonMark is standardized. GitHub, Reddit, Stack Overflow, Discord, and most documentation systems render it natively.15 If a future system can read plain text, it can read your Markdown.

What happens to my notes if MNMNOTE shuts down?

Nothing happens to your notes. MNMNOTE stores every note in your browser as Markdown text, owned by your origin. Export at any time. If the site goes dark tomorrow, your existing browser tab keeps the data; your exports remain Markdown files. The file is the contract — that is the whole architecture.

Doesn't the EU Data Act already solve cloud lock-in?

It is starting to. The EU Data Act's cloud switching obligations entered application on September 12, 2025, requiring providers to permit a switch within a transitional period defined by the regulation and to phase out switching fees by January 2027.12 But the law applies to providers operating in Europe and to a specific class of services. Local-first remains the only architecture that solves the problem at the file level.

Why not just rely on cloud exports?

Cloud exports are partial by design. Craft's own documentation notes that nested cards and toggles "can't be represented in linear editors, so they are flattened out."10 Notion's export of a database is HTML or Markdown that loses relations. Apple Notes exports as opinionated HTML. An export is a snapshot of the trip back to plain text — and snapshots, by definition, are not the territory.

Is local-first the same as offline-first?

Not exactly. Offline-first software keeps a cache of cloud data and reconciles when the network returns. Local-first software treats the device's copy as the authoritative one — sync, when it exists, merges peer to peer, often via CRDTs such as Yjs or Automerge.19 The difference is who is the source of truth. In offline-first, the cloud is. In local-first, you are.

What about collaboration? Doesn't local-first break shared notes?

It does not. The fourth Kleppmann ideal is "Seamless collaboration with your colleagues."7 CRDT research — Kleppmann's own Automerge, Kevin Jahns's Yjs, Loro — exists precisely to let local-first software merge concurrent edits without a central authority.19 Local-first collaboration is older than the buzzword; it just routes through the file, not through the company.


References

Grouped by tier. All URLs verified live as of 2026-05-15. Inline citations above use the numbered footnote keys below.

Tier 1 — Academic / primary research

Additional Tier 1 sources consulted:

Tier 2 — Mainstream press / regulatory

Additional Tier 2 sources consulted:

Tier 3 — Industry analysis / commentary

Additional Tier 3 sources consulted:

Tier 4 — Personal site / editorial voice

Additional Tier 4 sources consulted:

Tier 5 — Community / viral precedent

Additional Tier 5 sources consulted:

Tier 6 — Standards / official specs

Additional Tier 6 sources consulted:

Internal MNMNOTE references


Structured data

Article JSON-LD

Footnotes

  1. AppleInsider. "Evernote fires nearly every US employee as it shifts operations to Europe." July 10, 2023. https://appleinsider.com/articles/23/07/10/evernote-fires-nearly-every-us-employee-as-it-shifts-operations-to-europe. Accessed 2026-05-15. ↩ ↩2

  2. Roam Research. "Pricing." $15/month standard plan; five-year Believer plan available. https://roamresearch.com/pricing. Accessed 2026-05-15. ↩ ↩2

  3. Notion. "Pricing." https://www.notion.com/pricing and "Upcoming changes coming to our Plus plan." June 26, 2024. https://www.notion.com/releases/2024-06-26. Notion AI add-on at $10/user/month. Accessed 2026-05-15. ↩

  4. Ango, S. (July 1, 2023). "File over app." https://stephango.com/file-over-app. Exact quote: "In the fullness of time, the files you create are more important than the tools you use to create them. Apps are ephemeral, but your files have a chance to last." Accessed 2026-05-15. ↩ ↩2 ↩3

  5. Sivers, D. (March 2022). "Write plain text files." https://sive.rs/plaintext. Exact quote: "Plain text will be there. Will Microsoft Word? Evernote? Notion? Maybe. Maybe not. But plain text? Always. Everywhere." Has carried plain text files since 1990 across every device; written four books and 400 essays in plain text. Accessed 2026-05-15. ↩

  6. Newport, C. (2024). Slow Productivity. https://calnewport.com/writing/. Argues for ownership of the artifact over the chrome. Accessed 2026-05-15. ↩

  7. Kleppmann, M., Wiggins, A., van Hardenberg, P., & McGranaghan, M. (April 2019). "Local-first software: You own your data, in spite of the cloud." Proceedings of Onward! 2019, Athens. https://www.inkandswitch.com/essay/local-first/ and https://martin.kleppmann.com/papers/local-first.pdf. Seven ideals verbatim. Accessed 2026-05-15. ↩ ↩2 ↩3 ↩4

  8. Evernote User Forum. "Doubling the price??" Personal plan rose from $59.99 to $129.99. https://discussion.evernote.com/forums/topic/151478-doubling-the-price/. Accessed 2026-05-15. ↩

  9. How-To Geek. "What Google Reader's Shutdown Teaches Us About Web Apps." Quote: "If I don't have a useable offline backup, I don't have data." https://www.howtogeek.com/141754/what-google-readers-shutdown-teaches-us-about-web-apps/. Accessed 2026-05-15. ↩

  10. Craft Help Center. "Exporting Content from Craft." Stores notes in proprietary JSON database; nested structures flatten on export. https://support.craft.do/hc/en-us/articles/15281794476188-Exporting-Content-from-Craft. Accessed 2026-05-15. ↩ ↩2

  11. Doctorow, C. (January 23, 2023). "The 'Enshittification' of TikTok." Wired. https://www.wired.com/story/tiktok-platforms-cory-doctorow/. Verbatim: "Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves." Accessed 2026-05-15. ↩

  12. Greenberg Traurig LLP. "Cloud Switching Under the EU Data Act: Implications for IaaS, PaaS, and SaaS Providers." September 2025. https://www.gtlaw.com/en/insights/2025/9/cloud-switching-under-the-eu-data-act. Fee phase-out by January 2027. Accessed 2026-05-15. ↩ ↩2

  13. IBM Newsroom. "IBM Introduces New Software to Address Growing Digital Sovereignty Imperative." January 15, 2026. https://newsroom.ibm.com/2026-01-15-ibm-introduces-new-software-to-address-growing-digital-sovereignty-imperative. Accessed 2026-05-15. ↩

  14. Gruber, J. (March 17, 2004). "Introducing Markdown." Daring Fireball. https://daringfireball.net/projects/markdown/. Sole author, with feedback from Aaron Swartz; goal was readable plain text. Accessed 2026-05-15. ↩ ↩2

  15. Markdown — Wikipedia. List of adopting platforms (GitHub, GitLab, Reddit, Stack Exchange, Discourse, Codeberg, Qt, Swift). https://en.wikipedia.org/wiki/Markdown. Accessed 2026-05-15. ↩ ↩2

  16. Brand, S. / Kahle, B. The Long Now Foundation. https://longnow.org/. Concept of "the long now" referenced in Kleppmann ideal #5. Accessed 2026-05-15. ↩

  17. Logseq. https://github.com/tiensonqin/logseq. Founder Tienson Qin's repository. Self-described local-first, plain-text architecture. Accessed 2026-05-15. ↩

  18. Matuschak, A. "Evergreen notes." https://notes.andymatuschak.org/Evergreen_notes. Atomicity, durability, accumulation as the practice. Accessed 2026-05-15. ↩

  19. Local-First Conference, May 30, 2024. Recap of inaugural Local-First Conference, including talks by Kleppmann on Automerge, plus 2024 CRDT research by Stewen & Kleppmann at PaPoC 2024. https://evilmartians.com/chronicles/recapping-the-first-local-first-conference-in-15-minutes. Accessed 2026-05-15. ↩ ↩2 ↩3