[rubymamis]

You might like my own note-taking app, Plume[1] that's built with Qt C++ and QML. You can integrate a Kanban board (with underlying Markdown text) right within your document[2]. It's still a work-in-progress, so this is why it's not featured yet on the website. But I'll finish implementing it very soon.

Unlike Obsidian, Plume's editor is a block-editor. That gives it the flexibility of Notion (to put advanced blocks like Kanban within the same document, to do drag & drop, etc.) with the performance of native apps by utilizing Qt C++ and QML (actually, Plume is 4x faster than the fastest native block editor on macOS - benchmarks on the website).

EDIT: Also, Plume is opinionated compared to Obsidian. That means much better ease-of-use at the cost of extensibility. I believe this is a trade-off worth to be making. I know first hand the intimidation of starting to work with something as complex as Notion or Obsidian. Plume is taking the block editor abilities of Notion with the familiar Apple Notes UX/UI while all the data is still plaintext underneath.

[1] https://www.get-plume.com/

[2] https://imgur.com/NIgDLOU

[ghosty141]

Will it be open source?

[rubymamis]

Plume is built on top of my open source note-taking app Notes[1]. Since Plume is based on Notes, I'll of course comply with the MPL license and release all existing files that were changed (and must stay MPL licensed).

But I recently discussed my reasoning to go close-source[2]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4.5 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.

[1] https://github.com/nuttyartist/notes

[2] https://news.ycombinator.com/item?id=38584960

[ayewo]

> But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.

Why withhold the remaining 1%? If you aren't so confident about your decision to open source, there's no need to commit to that decision now.

It's good that you are leaving the door open, but keep in mind that if some folks suddenly become successful with a service that can turn any GitHub repo into a nice looking SaaS, at the click of a button and for a super low fee, I'm pretty sure you'll be hesitant to open source all your hard work so it can harvested.

[rubymamis]

Because I'm very much still a believer in open source. And you're right, that's a horror scenario I want to avoid. I'll only open source it in a way that won't compromise the sustainability of my work. I've yet to come up with the right model, so until then, it will stay close source.