> Particularly given that there appears to be no technical reason why none of the other add-ons are allowed any more, it being merely a policy decision. I already verified that my add-ons can still run on Firefox for Android but aren’t allowed to, same shouldq be true for the majority of other add-ons.

I wonder how the author did that. If it was a custom build of FF, we could rely on a fork as long as FF is open source and it supports extensions. If it is a configuration, I'll be happy to apply it to my FF.

Meanwhile I used ApkExtractor to save the APK of FF 68 on my phone (no root required) just in case I inadvertently upgrade FF on it. I already upgraded FF on my tablet and my old phone to test the UI. My take is that the new collections are good but the navigation UI is really bad. Opening new tabs, tapping the URL bar to go to a new site, forward button, they are all worse than in FF 68 and before. Hopefully they'll make them work as before.

I understand that staying on version 68 is also bad because of no security fixes. Furthermore it's possible that extension authors kill the Android version of their software. The plan is to wait for a while and see what happens.