I built a small app to read AI-generated markdown files without the clutter of a full editor
Hey everyone — wanted to share something I've been working on Meva.
I use AI tools (Claude, ChatGPT, Cursor) pretty heavily for work, and I kept ending up with a growing pile of markdown files — design docs, API specs, code explanations, architecture notes. Reading them was always annoying. VS Code's preview pane fights for screen space, most markdown apps are really editors with way more UI than I need, and nothing updated live when an AI tool was streaming output to a file.
So I built Meva — a native desktop app that just reads markdown. That's it. No editor, no toolbar, no cloud anything. You point it at a file or folder, and it renders everything nicely — LaTeX, Mermaid diagrams, code blocks — and updates in real time as the file changes. It's under 15MB and runs fully offline. Your files never leave your machine.
This project was a mix of manual coding along with frequently using Claude code for organization, code complete and even brainstorming with the feature ideas.
I've been using it daily in my own workflow and it's become my default way to read any .md file. There's a free version to try and a one-time purchase for the full version (no subscription).
Would genuinely love feedback — what would make something like this more useful for your workflow? Anything that feels missing or unnecessary?
usemeva.com if anyone wants to check it out.
Love the focus here. Most markdown apps try to be everything and end up being clunky for the simple "just read this file" use case.
The real-time updates while AI is streaming output is brilliant - I've definitely had that frustration where I'm watching Claude write to a file but have to keep refreshing to see the latest content.
One thought: since you're targeting AI-heavy workflows, integration with common AI file structures could be interesting. Like if Claude or ChatGPT dumps a bunch of files in a project folder, being able to quickly navigate between related docs or even show a simple file tree sidebar.
The offline-first approach is smart too. When you're dealing with potentially sensitive code docs or architecture notes, keeping everything local is a real selling point.
Keeping it minimal while adding thoughtful shortcuts (like the code block toggle) seems like the right balance. Congrats on shipping!
Thanks! The folder navigation you're describing is actually already built in — you can point Meva at a project directory and browse all the .md files with a sidebar. Give it a try and let me know how it fits your workflow!
Congatulations for the work, and how are you handling the security prospective of the platform.
Congrats on the launch, these are some impressive features. have you thought about lightweight features like saved reading views (e.g., collapse code blocks by default, focus mode, etc.) or is the goal to keep it radically minimal? Congrats either way!
Thanks. The goal is to keep it minimal and focused on the reading experience. I am getting many requests for keyboard shortcuts, and more people want to use it without a mouse. I plan to add a shortcut to toggle all code blocks.
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
Thanks, I appreciate it. So far, most early users have come through word of mouth and by sharing Meva on forums, blogs, and communities like Reddit and Hacker News. I also actively reach out to users who share feedback and use that to guide improvements. Early feedback has been especially helpful in shaping features like keyboard shortcuts and live file watching.
That's a strong start, especially by using Reddit and Hacker News early on. It's encouraging that features like keyboard shortcuts were developed based on user feedback.
I've noticed that while many founders post in broader communities (like r/startups or Hacker News), real traction often comes from smaller, niche subreddits where users are actively discussing specific workflow problems.
Out of curiosity, are you mostly posting on your own, or are you engaging in existing threads where people are already talking about file workflows and automation?
I'm happy to share a few ideas that I think could work well for Meva.