When people hear “local-first,” they usually think about privacy first. That is correct, but incomplete.
Local-first software also changes ownership. It determines who can keep using the tool, who can migrate away, and who absorbs the cost when a vendor changes direction.
For journaling, that matters because the value of the product compounds over time. A journal with five years of entries is not interchangeable with a blank note-taking app. If the software breaks trust, the user carries the cost.
Ownership needs more than encryption
Encryption protects the contents of your entries. Ownership also depends on whether you can:
- access the data without a server handshake
- move it to another format
- keep local backups under your control
- understand where the data lives
That is why Mini Diarium pairs encryption with an intentionally local-first design instead of treating export and backups as afterthoughts.
What local-first looks like in practice
In Mini Diarium:
- entries are stored in a local encrypted SQLite database
- the app can be used fully offline
- exports are available in JSON and Markdown
- imports exist for Mini Diary, Day One, and jrnl
- automatic local backups reduce the blast radius of mistakes
- the app makes zero network requests
Those are not isolated convenience features. Together, they define whether the app behaves like a tool you own or a service you borrow.
Portability is part of trust
Trust is not just “we will behave well.” Trust is also “you can leave.”
That is why export paths matter so much in private software. If a journaling app makes it hard to get your writing out, it is asking for a one-way commitment. That is exactly the kind of leverage a privacy-first tool should avoid.
Mini Diarium keeps export simple on purpose. JSON preserves structure. Markdown keeps a human-readable path available. Neither format makes every future migration effortless, but both keep the exit door open.
Local-first keeps the product honest
One useful side effect of local-first architecture is that it constrains product behavior:
- fewer opportunities for hidden telemetry
- fewer incentives to gate basic access behind accounts
- fewer reasons to entangle usage with recurring service infrastructure
That pushes the product toward clarity. Either the app is useful on your machine, or it is not.
Why this is the right scope for Mini Diarium
Mini Diarium is a journal first. The goal is not to become an all-in-one life platform. The goal is to give private writing a stable home on hardware the user controls.
That is also why the project keeps public documentation close to the code:
Local-first journaling is a practical position, not an aesthetic one. It keeps ownership where it belongs: with the person doing the writing.