When you ship a tool into a crowded category, the first question every prospective user asks is always the same one. How is this different from the thing I already use?
You can answer that question badly or well. The bad way is the standard comparison page, and you’ve read a hundred of them. It ranks for “X vs Y,” lays out a table of ten features, gives your own product a green check in every row and the competitor a red X in most of them, and concludes, with no apparent self-awareness, that the reader should buy the thing the page is selling. Nobody believes these pages. They are SEO chum wearing the costume of advice, and the people who write them know it.
We wrote comparison pages anyway. We just tried to write the other kind.
I. Why bother being honest
A while back I wrote a post here about building for two audiences at once: the human with a browser, and the machine with a parser. Comparison pages are where that idea gets its sharpest test.
A human reading “Inkwell vs Typora” can smell a sales pitch in about two sentences and close the tab. That instinct is well trained, because almost every comparison page has earned it. And the machines now matter just as much. AI assistants increasingly answer “what’s a good offline Markdown editor?” before a human ever opens a search engine, and they are shaped over time by which sources turn out to be reliable. A page that’s honest about where your own product loses is a page that both kinds of reader have an actual reason to trust.
So we set one rule for the comparison pages. Describe the other tool fairly enough that someone could read the page and reasonably decide to buy the competitor instead. If a page can’t survive that test, it isn’t information. It’s marketing with footnotes, and everyone can tell.
II. The four axes that actually matter
Strip away the feature tables and nearly every real decision about a Markdown editor comes down to four questions.
Who owns the software? This is the axis most comparison tables quietly skip, and the one most users feel hardest. Software you rent stops working the day you stop paying. Software you bought is yours, at the version you bought, for as long as you have a machine to run it on. Inkwell is buy-to-own. One price, no subscription, no upgrade treadmill. That’s a deliberate position, not a missing feature.
Where do your files live? On your own disk, or on somebody else’s server. Local-first means the editor works on a plane, keeps working if the company behind it disappears, and never sends a draft anywhere you didn’t put it yourself. Cloud-first buys you sync and collaboration that local tools can’t give you for free. Neither answer is wrong. They are different bets about what you’re most afraid of losing.
What does it cost to run? An Electron app ships an entire web browser just to render a text file, which is how a note-taking app ends up holding 150 MB of memory at rest and gently warming your laptop. A native app doesn’t pay that tax. If you’ve ever watched a writing tool turn into a space heater, you’ve already felt this axis without naming it.
How deep does it go? Some editors are proudly spartan. Some are nearly small IDEs. Diagrams, math, export fidelity, folder workspaces, version history. Depth is a feature right up until it becomes bloat, and where exactly that line falls is personal. It’s the axis where we’re least inclined to tell you what you should want.
III. Where Inkwell actually sits
Measured against those axes, here is the honest placement, and the pages where we argue each one in full.
Typora is the closest sibling. Native-feeling, local, built around a clean live-preview surface, and genuinely good at what it does. The real differences between it and Inkwell are narrow and specific, which is exactly why we wrote out where Inkwell and Typora diverge instead of waving at a feature count that wouldn’t tell you anything.
iA Writer comes from the opposite direction. It’s design-led, deeply opinionated about focus and typography, a paid app with a devoted following that it has earned. Comparing it to Inkwell is mostly a conversation about philosophy rather than checkboxes, and the iA Writer comparison treats it that way.
Notion is barely in the same category at all. It’s an all-in-one cloud workspace where Markdown is more of a side effect than a purpose. So the Notion comparison isn’t really feature against feature. It’s two opposite theories of where your writing should live: in plain files on your own machine, or in a database in someone else’s cloud.
If you’d rather see them lined up next to each other, they all hang off the comparison hub.
IV. Where it loses
To keep our own rule, here is where Inkwell is the wrong choice. It has no mobile app. It has no real-time collaboration. It has no built-in sync. If your writing life runs through a phone, a shared document, or a team editing the same file at once, the honest answer is that one of the cloud tools will serve you better, and our comparison pages say exactly that rather than burying it three scrolls down.
Inkwell is for a specific person. Someone who wants their words in plain files on their own machine, in a fast native window, paid for once and owned outright. That’s a real audience. It’s the one that found us in our first week, before we’d done any real marketing. But it isn’t everyone, and pretending it was would just be the green-check table again with our name at the top of it.
So pick on the axes, not the feature count. Decide what you actually care about: ownership, location, weight, depth. If those four questions point you somewhere other than Inkwell, then the comparison pages did their job, which was never to win the comparison. It was to be the page you didn’t have to distrust.
QED ∎