Expand Add-on Compatibility in Firefox for Android.

[MintMain21]

Unlike some other users, I'm a fan of the "Daylight" update to Firefox for Android in 2020. I think the new UI is slicker and easier than the competition, but from the beginning there was always room for improvement.

For me, my biggest concern with Daylight has always been the Add-On Compatibility, or lack-therof. I appreciate how Nightly allows me to curate my own Add-On Collection to try add-ons and use ones I like, but after a year and a half since Daylight launched I feel like expanded Add-On support shouldn't be limited to Nightly, especially since Nightly is, by nature, an unstable build.

I propose two solutions to improve Add-On support on Android.

1. Port over the current Custom Add-On Collection feature as-is to either Beta or Stable (this would include hiding it as a "secret setting" behind the Firefox Logo on the About Page).

2. Curate a larger collection of Add-Ons tested for compatibility on Android that could be given their own unique badging on the Add-Ons site, and in turn installable on any Android build of Firefox.

The former-most option would be the easiest to apply for the sake of those willing to use Nightly's fix, but the latter-most option would be more user friendly, improve user participation in the Android Browser's development (by allowing users to submit recommended extensions for Android similar to how the general Recommended badging works), and free up Nightly builds for testing Extension features that have yet to be perfected on Android.

Mobile-Android

[ESullivan]

Hello Everyone!

Posting a link to our announcement from last week regarding expanding the extension ecosystem on Android.

Thanks!!

[Jon]

Marking this as 'Delivered' - click here to read more about the exciting news.

Thanks all for your role in making this happen and we look forward to continuing to collaborate with you here on Mozilla Connect 🙌

Share your next great idea.

[JimCarner]

Despite the "good news" I received via email, the add-on "I still don't care about cookies" isn't available yet on Firefox for Android.

"I don't care about cookies" is available, but the developer sold out to Avast, so I no longer trust that add-on.

"I still don't care about cookies" is a fork of "I don't care about cookies" and it's what I use on Firefox on Windows 10 (as well as uBlock Origin).

Please add "I still don't care about cookies" to Firefox for Android.

[ESullivan]

Hello - only the extension developer can publish an Android compatible version.

[JimCarner]

Well I checked a couple of days ago and "I still don't care about cookies" is now available for Firefox on Android.

I installed it and it's working perfectly. It even suppresses the incredibly annoying ever-present Google notification, although it takes a second or two for it to go away.

[Paincake01]

Expanding addon compatibility and themes for android.

There are many good addons available right now, but i am missing a few from my desktop collection. Increasing addon compatibility with android will help.

Also i miss using the themes for desktop. It just gives a person touch to web surfing.

[brixter]

History Cleaner addon is still not available in Firefox Android.

[regs]

This says Delivered, but there are still a lot of addons not working. Like Menus API not working at all. Nothing comes up in context menus. Start page dial addons not working, even with enabled Composed homepage.

[ESullivan]

Hello @regs. Supporting extensions on Android is what was delivered. Whether or not to make an Android version of their desktop extension available is up to each individual extension developer.

[regs]

But WebExptensions API in Android version is incomplete. Extension developer can't add anything to context menus, as Menus API isn't implemented. Also composed pages appears empty.

[brixter]

@ESullivanWebextensions History API is also not compatible in Firefox Android. Extension developer cannot access the Firefox history in Android because of this.

The ball is on Mozilla's court, not the extension developer.

[ESullivan]

Ah sorry, I misread the post. There is not parity btw desktop and mobile APIs as you pointed out. I am not certain which additional APIs may land in Android in the future, but if I get any info I will post back.

[ESullivan]

Checked in with the Engineering team and all the APIs mentioned are in their backlog, but I don't have any timing to share at this point.

Also, @regs the team was not certain what was meant by, "composed pages appears empty" - any clarification is appreciated.