Every few weeks, someone emails asking for the same thing: editing. “Love Meva, but when will I be able to edit files?” “Can you add inline editing?” “I want to make checklists clickable.”
The answer is always the same. Meva is read-only by design, and that is not changing.
This is the explanation I wish I could attach to every one of those emails, because “it keeps things simple” is true but it is not the real reason.
The greedy algorithm problem
Each editing request is completely reasonable on its own. Fix a typo without switching apps. Check a box. Small things.
But software does not work that way. Allow typo fixes and you need an undo stack. Add undo and you need text selection. Add selection and someone wants formatting. Every step is small and sensible, and at the end you have built an editor. A mediocre one, built by people who spent years optimizing for the opposite thing.
It reminds me of a greedy algorithm. Every step looks like the best next move, and the path walks you straight off a cliff.
The world has excellent editors. It does not need one more.
Reading and writing are different postures
When you write, the interface should serve your hands. Cursor, shortcuts, undo, all of it. When you read, the interface should disappear. A book does not ask you to hold a pen, and that is part of why you finish the chapter.
Every tool that tries to do both ends up mediocre at both. The reading view gets cluttered with editing chrome. The editor gets constrained by reading layout. I did not want Meva to be mediocre at two jobs.
What read-only makes possible
This is the part people miss. Read-only is not just the absence of features. It is what makes the good parts possible.
It opens instantly. No document model to initialize, no editing state to restore, no cursor to place. The app renders the file and gets out of the way.
Live reload never conflicts. When Claude Code rewrites a file on disk, Meva re-renders it immediately. If Meva held editing state, every external change would be a question: did the user have unsaved changes? Where was their cursor? Read-only means the file on disk is the truth, always.
There is nothing to lose. No “unsaved changes” dialog. No autosave to configure. No sync conflicts. You cannot lose work in Meva because there is no work to lose. That sounds trivial until you have lost an hour to a note app.
You actually read. A reader with an edit button is a reader you are tempted to fiddle with. I notice it in my own use. Open a document in Meva and I read it. Open the same document in an editor and I start fixing the formatting.
The requests, honestly answered
Inline editing usually means “let me fix a typo without switching apps.” Fair. But see the greedy algorithm above.
Clickable checklists feel like reading, but checking a box is a state change, and state changes need persistence and conflict resolution. A Pro customer once offered to build this themselves and contribute the code. I said no, and it was not easy, because the request was reasonable. But a checklist you can check is the first step toward becoming something else.
Multi-window support is the interesting one, because it does not violate the principle. Multiple windows for reading is still reading. It is the rare request I do not have a philosophical objection to.
If you need to edit
Use an editor. Typora, iA Writer, Obsidian, VS Code are all wonderful at what they do, and I will happily name them. Meva is not competing with them.
The workflow we see most: people write in their editor of choice and read in Meva. The tools coexist because they do different jobs. If you need one tool that does both, Meva is not it, and I would rather tell you that now than ship a compromised version later.
The trade
Saying no is harder than saying yes. Every no is a customer walking away, and we have watched it happen. The refund requests sting. The “I’ll switch when you add editing” emails sting more, because the people writing them are not wrong.
But every yes to editing would be a no to something else: the instant launch, the clean interface, the feeling that the app is never in your way. Every product is a bundle of trade-offs. The honest ones say what they traded.
Meva traded editing for reading. Perhaps the hardest feature to build is the one you leave out.
Meva is a read-only markdown reader for Mac, Windows, and Linux. Free at usemeva.com.
Related posts: - Reading Claude Code Output Without Losing Your Mind — Claude Code-specific guide - Best Markdown Viewers for Mac in 2026 — honest comparison - Why AI Tools All Output Markdown — category explainer