Concretely the MVP can:

1. Open, edit, and save a Markdown file: real multi-line editing with a visible and correctly-placed cursor.
2. Move and edit modally: a working NORMAL/INSERT distinction and enough of the SPC leader keymap to feel like Doom Emacs’s.
3. Render prose beautifully: proportional shaping (if the expression is right) of text, not a rigid character grid, and basic Markdown syntax styling.
4. Save invisibly to git: every save creates a background snapshot, the writer could also save (read commit) milestones, or special forks of his work, all without seeing any of git’s intricacies.
5. Stay out of the way: which-key hints and a discoverable command palette, for minimal writer-tool latency.

Everything else is post-MVP and explicitly out of scope. I name the boundary now as my north star to ship as fast as I can. The discipline of a named MVP is what lets a solo founder ship, and this very five-point roadmap will keep me ruthless about scope.

Speaking of “shipping fast”; I’m not in a hurry to get the product out in the traditional way, because the aim is also for me to learn while building, and boy there are things to research and learn about; both in regards to the tech stack and the writers craft. For example, some of the technical questions I want to answer before or while building the app:

• How text editors are built and do I need to start from scratch?
• What should I research before start building: I know that text rendering and editing is hard, I’ve read one or two things on the subject once, but how come we already have so beautiful and efficient text editors since decades? There have to be some known “knowns” to start from.
• Will the core of the app be a simple combination and orchestration of some libraries or will I have to dive deep into text manipulation specific data structures and algorithms?
• Autographe needs low latency as a feature so that the gap between keystrokes and pixel is imperceptible, but how to model all of that the right way from the start?
• How should I approach modal editing à la Doom Emacs and Spacemacs: will it be a state machine? How will that map to the gui level I’ll be using?
• how much “work” is already handled at he OS and framework levels? How much do I need to build myself?

At this stage, the question list has no limit, every question has layers of related questions.

Honestly, the vision is blurry; there are plenty of prose text editors, not all of them are successful commercial products, prose writers have already their favorite tool, the technical domain is hard!

Certainty of death? Small chance of success? What are we waiting for?

— Master Gimli

Exciting times ahead. Let’s get into it.

Why yet another desktop app for writers, isn’t there enough of them?

The software development industry has gone absolutely crazy with AI. Developers of all levels are using LLMs to produce code to the detriment of their hard-won skills. Not long before, we were arguing about, and almost shy talking about the myth of the 10x programmer; today everyone and his dog is developing apps, they are effectively a 100x developers in terms of the amount of code produced.

Autographe is like an antidote for me, an attempt to preserve my software craftsmanship and stay true to my values: producing software crafted by a human for humans. I want to do it “à l’ancienne”, no Claude, no Codex, no Cursor, no LLMs, just me and my hands.

That was you, what about writers?

I’ve always wanted to be some sort of writer, but never got the time nor energy to work it out. Fortunately I read a lot; and as a reader, I’ve learned that writing is a huge intellectual endeavor that comes way before the styling aspect of it, that most readers are going to judge. Unfortunately, AI enshittification made its effect on so many writers (or pseudo-writers should I say), and the results, even at this early point of AI history are so bad: masses of text that are banal, generic and shapeless.

What made things worse is that writing apps started including AI services. Writers can now be more productive (more text in less time!) thanks to AI! This is insane! I don’t want to read “productive” writers text, I want them to take their time!

So Autographe will be my response to today’s prose writing tools, an app that:

• empowers true writers to write in their own words in their keyboard
• is local-first: no remote server
• no AI, with intuitive file based organization
• has a clean design optimized for flow: writers will write, the app will disappear while they write
• offers real productivity with a modal-first editing (à la Emacs and Vim)
• has intuitive version control powered by Git: for writers, not for developers
• markdown based

Autographe for writers is what Emacs or Vim is for developers

A macOS app, built for maximum snappiness, and true/genuine writers happiness.

AI usage is eroding craft, I’m building an antidote for myself and for writers who feel the same. I’m very excited and honored to start this project. No growth hacking for this one, no build-in-public bullshit, I’ll take my time to work on it, get feedback, optimize and use it myself. If some day, a dozen writers are happy with it, I’ll consider myself a hero.

Autographe is text written by your own hand.

اللهم لا علم لي إلا ما علمتني إنك أنت العليم الحكيم.

اللهم لا فهم لي إلا ما فهمتني إنك أنت العليم الحكيم.

ربي اشرح لي صدري ويسر لي امري واحلل عقدة من لساني يفقهوا قولي.

اللهم اجعل عملي كله صالحاً ، واجعله لوجهك خالصاً ، ولا تجعل لأحد من خلقك فيه شيئاً.

اللهم آمين ، و صلى اللهم و سلم على نبينا محمد وعلى آله وأصحابه ومن تبعهم بإحسان إلى يوم الدين.

وسيم