This is good. Now, all extensions marked by the developer as being compatible with Android are shown on AMO. (If you toggle to Desktop mode, you can actually install any other extension on AMO, too.)<p>The baffling thing is why this took so damn long. FF for Android supported add-ons from the beginning. That's the best thing about Firefox for Android! They decided to rewrite the UI in 2020, and there were fair reasons to do that. Obviously this required some reimplementation time for extension support.<p>But they then launched the rewrite of FF for Android with extension support... but hidden. Only a small set of recommended extensions were enabled, and a few were drip-fed over time (that is, added to the list). Thankfully, this included the single most important extension, uBlock Origin, from the very beginning. (The lack of uBO why Chrome for Android is borderline unusable for me!)<p>But from almost the very beginning, we've also had the ability to activate custom extension collections in Nightly (and in Fennec F-Droid, which is a rebuild of stable Firefox). The vast majority of extensions worked fine for... well, years now.<p>So why in the world was this delayed the whole time?
I'm so grateful that FF for Android exists with addon support. Using it with uBlock is the only way to make mobile not an awful experience for me.
Excellent, finally in stable. Have been using Nightly and more recently Mull specifically for extensions like 'I still don't care about cookies', 'ublock origin' and 'dark reader' which make the web on mobile at all practical.<p>Firefox browser share is like 2-3%. Please consider using it, the internet will be a lot shittier without Firefox as an option, and it is the best option for privacy and ad-blocking.
This was a clincher for me that made me switch from Chrome/Chromium on my Pixel. Previously, I was using Kiwi Browser because it supported Chrome extensions however while it works it has a lot of annoying quirks. I just couldn't stomach the experience of browsing the web without an ad blocker though. Now Firefox and UBlock work on Android, Firefox has quickly become my preferred browser. Still using Chrome on desktop though for now.. maybe that'll change too!
Thanks to Firefox extensions I get an automatic dark mode on HN, and almost any other website, as soon as my device is switched to dark mode. Normally this would have to be supported explicitly in the website CSS.
Great! Now I can finally install an extension to autodelete cookies for certain domains. This feature is available on stock Firefox Desktop but not Mobile.
One of the newly-available extensions is mine for Hacker News [0] - it highlights new comments when you revisit an item and somewhat improves some of the UX on mobile:<p>[0] <a href="https://addons.mozilla.org/firefox/addon/hn-comments-owl/" rel="nofollow noreferrer">https://addons.mozilla.org/firefox/addon/hn-comments-owl/</a>
This is great news. On GrapheneOS, every time I use the stock browser without the benefit of my uBlock Origin setup, I feel a bit creeped-out and violated.
Best news in the mobile browsers' space since Firefox supported extensions!<p>If Firefox goes back to being THE browser of choice for tech savvy people, I'll stop thinking I made a bad choice supporting it everyday since it came out.<p>Sometimes a joy.
You could get extensions working on FF for Android, for some time now, by setting a custom collection ID, allowed in the Beta version.<p>The problem is that many extensions have been incompatible with Android. And of those compatible, many have poor UX. For example, LeechBlock has been compatible and listed as available for some time, but its settings page isn't mobile-friendly. And LeechBlock can't restore settings from “sync storage”, you have to load them from a local file (on mobile, having local files is a challenge in itself). Many people may have a bad experience.<p>On the other hand, extensions are the primary reason to use Firefox on Android. Therefore, I'm glad about this news.
The 2nd most important addon after unlock origin is Multi-Account-Containers: <a href="https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/" rel="nofollow noreferrer">https://addons.mozilla.org/en-US/firefox/addon/multi-account...</a><p>This would enable proper isolation between browsing contexts, and therefore make progressive web apps truly usable and a good alternative to native apps.
Currently PWAs leak cookies to the browser, therefore you cannot login on the PWA while browsing "anonymously" in the browser.
> where we’re the only major Android browser to support an open extension ecosystem<p>Uhm, Kiwi browser is Chrome-based and supports Chrome-extensions on Android and has for years. It's pretty great.
Can anyone recommend an extension that can be used to limit the total number of tabs in Firefox for Android? "Limit Tabs"[0] works great on the desktop and I was hoping it would become available on mobile now, but sadly it didn't.<p>[0]: <a href="https://addons.mozilla.org/en-US/firefox/addon/rudolf-fernandes/" rel="nofollow noreferrer">https://addons.mozilla.org/en-US/firefox/addon/rudolf-fernan...</a>
Last time I check Firefox on Mobile still break sites' layout and not render video player properly (cannot touch seek and play/pause button, it's under view window) on my Samsung Note 10. I love Firefox but it needs to be at least usable.
If it wasn't for extensions collections that allowed all extensions alll along, I would have quit Firefox a long time ago.... About time they get their head out of their asses
This is progress, but Mozilla needs to do more. Firefox for Android still lacks the ability to sideload add-ons, a feature that works on the desktop version of Firefox. This means Android users aren't able to install extensions outside addons.mozilla.org (AMO) unless they switch to a Firefox alternative that supports it, such as Iceraven[1] or SmartCookieWeb-Preview.[2]<p>For me, the most important add-on that has been removed from AMO is Bypass Paywalls Clean, which is the easiest way to bypass paywalls on popular news sites. In April of this year, a French website filed a DMCA copyright takedown notice, causing Mozilla to remove the extension from AMO.[3] The add-on developer (magnolia1234) did not want to challenge the DMCA notice, probably because it would require them to break anonymity and be subject to legal liability.[4]<p>Fortunately, in September, another developer (dbmiller) was willing to reupload the add-on to AMO as "Bypass Paywalls Clean (D)" with no changes.[5] The hope is that dbmiller will keep this add-on up to date with the source and challenge any DMCA notices filed against this new upload.<p>However, the fact remains that Bypass Paywalls Clean was unavailable on Firefox for Android for 5 months because the browser did not allow sideloading. In the announcement, Mozilla says their mission is to maintain "an open and accessible internet for all" and that extensions are meant to help users obtain "more personal agency out of their online experience". To achieve this mission and better distinguish Firefox from browsers that gate add-ons through app stores (Safari on iOS), Mozilla should allow users to enable sideloading on Firefox for Android as an option.<p>[1] Iceraven: <a href="https://github.com/fork-maintainers/iceraven-browser">https://github.com/fork-maintainers/iceraven-browser</a><p>[2] SmartCookieWeb-Preview: <a href="https://github.com/CookieJarApps/SmartCookieWeb-preview">https://github.com/CookieJarApps/SmartCookieWeb-preview</a><p>[3] <a href="https://www.ghacks.net/2023/04/20/mozilla-removes-bypass-paywalls-clean-extension-from-its-add-repository/" rel="nofollow noreferrer">https://www.ghacks.net/2023/04/20/mozilla-removes-bypass-pay...</a><p>[4] <a href="https://gitlab.com/magnolia1234/bypass-paywalls-firefox-clean/-/issues/905" rel="nofollow noreferrer">https://gitlab.com/magnolia1234/bypass-paywalls-firefox-clea...</a><p>[5] Bypass Paywalls Clean (D): <a href="https://addons.mozilla.org/en-US/firefox/addon/bypass-paywalls-clean-d/" rel="nofollow noreferrer">https://addons.mozilla.org/en-US/firefox/addon/bypass-paywal...</a>
We've had lots of news about this coming for months, but with Mozilla's quite low market share, and the share of those users that use extensions - who's really caring about this other than some power users?