For my notes app, I’ve been experimenting with using local plain-text #Markdown files, while also keeping a #SQLite database that stores exact replicas of these files.
The SQLite database is used only for indexing, which should make keyword searches in notes much faster. #dev
Replies (4)
Just out of curiosity, why not use Joplin?
I don't think Joplin has a live-preview feature like Obsidian does.
Basically, when you select some text with styling applied, it will show the Markdown syntax. Then when unselecting, it will hide the syntax again.
I really like this approach, and I have a semi-working solution for my app. Still working on code-blocks.
I use logseq + MarkText like that. Logseq provides the indexing for fast searches and let's you link anything with anything. But, I use MarkText for documents or when I want to work in raw markdown. And, I use them together, because the current version of Logseq is all markdown files you can open both from your filesystem and from within Logseq (open with external app).
I'm concerned about the next major release of Logseq, which will put it in a database. In theory, it will increase perf and scalability. But, my flow requires a lot of filesystem integration between tools, so I'm not sure that will work for me. But, the current Logseq 10.x is great with my current flow.
My plan is to keep notes local, but then have a database alongside that will make stuff like version control much easier to integrate. You know how on Google Docs you can go back and see previous versions of your document - I want to do the same in my app.
This will also be really nice for when I at some point implement collaboration features. Basically, allowing people to invite other users into their app and edit their note documents together.
