Where Plainva is headed
Shipping v0.1 didn’t feel like crossing a finish line so much as opening the door and letting people in. Which means the question I get most right now isn’t “what does it do,” it’s “what’s next.” Fair enough — here’s the honest version.
What’s bugging me most right now
It’s the “unknown publisher” warning you get installing Plainva on Windows or macOS today. Nothing dangerous, just a bad first impression for an app that’s asking you to trust it with your notes, so proper code-signing is high on my list. Behind that sits the less glamorous work: richer templates, more power in the database views, and keeping Plainva quick once a vault gets genuinely large. None of it makes for an exciting headline. All of it decides whether people actually stick around.
The one I’m actually excited about
Mobile. I didn’t bolt sync onto Plainva as an afterthought — the whole architecture assumed from day one that a phone would eventually need to open the same vault. So the mobile app isn’t a separate product with its own quirks; it’s just another window onto the notes you already have on desktop. It’s in closed testing on Android and iOS right now, widening through the summer — the thing everything else has quietly been pointing toward.
Whatever changes underneath, some things won’t: plain Markdown files, local-first storage, no lock-in, the AGPL license. Everything above gets built on top of that, never around it. If you want to help shape any of it, open an issue or start a discussion — right now there’s very little distance between your feedback and what I build next. And if you’d rather back it than file a bug, sponsoring keeps the project independent. Either way, thank you for showing up this early.
- Try it: plainva.com · Source: github.com/plainva/plainva
— Marco