I respect his decision, but I don't understand it honestly. A lot of worrying about bad reviews? Or if it's pulled from the play store, worry about losing users? Why is that even a concern? Oh well. If he doesn't want to work on it anymore that's all the justification he needs.

ohh, there's a tweet, however I'll have to see if it'll allow using openkeychain, instead of TB's own librnp, which I really dislike on the desktop, and use sequoia octopus librnp (on top of gnupg) instead.

I really don't like TB's way to keep and maintain keys (I use the gnupg "external" key for my private key, but still TB's librnp wants to have it stored in its own DB for no reason, otherwise can't do a thing). And the same that applies to FF applies to TB, they shouldn't attempt to keep passwords and keys themselves, better use gnupg, and for passwords something like qtpass on the desktop, and for android, there's openkeychain and others... And they have watched how it's possible to do something like the sequoia team does, but I guess they like what they chose to do, :( Using sequoia octopus librnp on mobiles might be rather complicated (it's somehow tedious to use it on distros not officially supporting it, since TB's changes lately tend to break octopus, and besides one needs to keep replacing the library on every TB's upgrade)...

But for those using big corps email providers, then yes, TB on Android is good news. In general it is good to have TB on mobile as well, I just hope they would provide more options to users., extensions for gnupg are all banned (admittedly enigmail was mangling too much into the TB's code), and they don't like autocrypt either, so no options...