[projektfu]

F-Droid has a number of apps.

KeePassDX (also on F-Droid) also supports TOTP, as does KeePass 2.0 on desktop, if you're comfortable keeping it with your password manager.

PyOTP contains plenty of information about how to implement an authenticator app.

https://pyauth.github.io/pyotp/

[mort96]

I would avoid anything KeePass, simply because it seems like an absolute mess of forks. How do you know which KeePass* to use? How do you know the one you pick won't be superceeded by another fork in 2 weeks? Why does the world need KeePass, KeePassX, KeePassXC, KeePassDX and KeePass 2?

[projektfu]

The original, KeePass 2, is quite good. The prior version is only for the old database format. The nice thing about it is you can automate sync in many ways, and it has plug-ins that do lots. Every other tool uses KeePass 2 databases.

I used KeePassXC but it didn't sync like I wanted using syncthing. Other synch stories probably work better, like Dropbox.

Kee is the browser extension I use and it's pretty good. They also have a sync service you can buy, but it's free to use with KeePass 2. I liked it better than the extension that's compatible with KeePassXC.

KeePassDX is pretty great. It's working well with my setup, especially using Brave as I avoid Chrome. Incidentally, I think recent Chrome updates have complicated things for password managers on Android but alternative browsers work great. I use it with a longer timeout to lock the database than the default.

I think KeePassX is superceded by KeePassXC.

So, if you ignore most of the other forks, you don't need much analysis paralysis, and everything works well.

For iOS, it's hard to find FLOS solutions but there are paid apps that are supposed to work well to integrate with KeePass 2 databases.