Published

Release 2026-10 is out! 🎉

The journey continues.

The road so far

It has already been over a month since the last blog post. And wow, was that a ride. After the website has launched, the numbers were alot bigger than anticipated. Not only from the nura conference (previously postmarketOS), but the Fediverse had big shares in it. Likewise, the frequency of interaction on Codeberg reached an all new height. Nonetheless I and some other people still found time to work on new stuff for BitRitter. Big thanks go out to baarkerlounger, who did a lot of UI rework. The app has never looked so modern and polished. Feature-wise, we got an important contribution from trevor, who was a first time contributor, in the form of app-based multi-factor authentication. A feature which has enabled a lot of users to use the app in the first place. I (Chfkch) have mostly doing review and merge work, besides some minor patches like the vault switcher - for those of you who have to juggle more than one. Well, obviously beside preparing for the first real, proper release.

Use the momentum

Currently, the project is more active than ever. There have been contributions from several people, some for the first time, some are long-standing contributors. Also, there has been a combined effort to push serveral things which are not directly related to writing code over the finish line:

  • Flatpak tooling
  • Flathub application (still ongoing)
  • CI improvements
  • Translations
  • Testing & opening/commenting on issues With this, there are plans for the next release, which is targeted around the end of the year (maybe even as a christmas present). A roadmap of these plans will be available in the README file and with some delay also on this website, so stay tuned.

What has been learned

Maintaining an app like BitRitter has been mostly coding on my own during the last two years, but now i see, that the community is not only a userbase, but also a valuable resource.

For detecting issues - that is obvious.

For helping me improve - sure, i am no professional in this sector.

For keeping me motivated - Heck yes!

For pushing so much code - i never knew that would happen.

For showing me what i lacked - mostly in polishing the UI, but also some neat tricks around Rust.

That said, i really want to thank everyone who participated. As cheesy as it sounds, without YOU, it would not happened the way it did!

A note on the version numbering

I think it does not make sense for me to follow the Semantic Versioning scheme. First, BitRitter is not a library, which is consumed, so breaking changes are less likely to happen and mostly not that bad should they happen. Second, it was very hard for me to figure out what should be in a release and if the number goes up at which place. To take this burden away from me, i will switch over to a YYYY-MM scheme, where YYYY is the year and MM the month of the release. Should there be a security or bugfix release in the same month, there will be a -XX suffix where XX is the incremented number of releases during that month. This will hopefully lead to more regular releases.

Outlook on 2026-12

So, since the interval here is rather short (in my terms of time), i do not plan to aim too high: The plan is to put a version of the Edit mode online which truly works. I don't want to be responsible for corrupted vaults... Maybe we will see a password generator, but it is settled yet.

Also, polishing will be an important taks here: First of all, the user-facing messages (mostly in the form of Toasts) will be refined. But also console output (should you start it in the terminal - for debug info etc.) will be improved.

SSH Keys do not have a proper Detail Page yet, this might fit into 2026-12 aswell.

Folders and Organisations support will most likely not make the cut, sorry about that.