It’s desktop extensions. Most mobile browsers only support a subset of all available extensions (including Firefox!). Now, Firefox will support its whole library of extensions.
They only mention “open extension ecosystem” idk if that means everything and also I haven’t found an extension not working on mine yet I have even installed a flash player extension for flash games on my browser so no opinion on those statements
The title: "Prepare your Firefox desktop extension for the upcoming Android release"
End of the first paragraph: "Here’s everything developers need to know to get their Firefox desktop extensions ready for Android usage and discoverability on AMO…"
End of the second paragraph: “so why not start optimizing your desktop extension for mobile-use right away?”
also I haven’t found an extension not working on mine yet I have even installed a flash player extension for flash games on my browser so no opinion on those statements
And those were installed from the mozilla addon library? With full support for a mobile interface? And you tried every extension available?
I have even installed a flash player extension for flash games
What u highlight desktop for, the article is about android and the 10 extensions it has so far, your own highlight says “about upcoming android release” desktop is only mentioned for devs to optimize their shit for mobile use.
And no my extensions were not from mozilla thats my whole point I can get extensions elsewhere this whole time, which is why I mock mobile mozilla users in the comments thinking mozilla did something revolutionary.
That was definitely the most infuriating thing they’d done with the mobile browser. The whole project started decades ago with a simple plan: make the most bare-bones browser, and let people customize it with any extensions they wanted. Then all of a sudden, it turned into having <10 approved extensions, and fuck your customization.
It’s gotten much better over time since then, but damn if there weren’t a few really bad years.
I think they went evil because letting google pay 80% of your bills isn’t really tenable… but some incredibly boneheaded decisions. Instead of offering their own suite of privacy focused products they tried to cram pocket down everyone’s throats.
I love Firefox but they have made some crushingly bad calls over the years.
It does make me suspect that when Google first funded them, the real handshake had little to do with using them as their default search engine, and instead had to do with cutting back on their focus on privacy to pursue literally anything else. But that’s just a conspiracy theory of mine.
Google funds Firefox so that it serves as a controlled opposition and to avoid antitrust action. However, most of the stupid decisions by Mozilla are self-inflicted by top management who are more focused on being an NGO than a tech company.
Didn’t know that. I also got some kind of shady vibes from Kiwi, but never run into any issues with it. Firefox was causing all kinds of problems with pages failing to load so I bailed, but would be glad to return if they fix the bugs and add full extension support.
This article was weird for me also I have all my extension already installed like bitwarden for passwords and all kind of adblockers and scriptblockers
Kudos to them for rolling out support more widely, but it’s a bit misleading as Firefox nightly/Fennec has supported extensions for years (albeit via a cumbersome process), and Kiwi Browser is also a thing.
I can’t understand how folks out there are just rawdogging the Internet out there without ublock or at least a DNS ad filter. Admittedly, Chrome runs a hair more smoothly, but the ability to use extensions like uBlock / DarkReader / Consent-O-Matic make the Firefox experience a tier above.
I just hope this makes it possible to install the Bypass Paywalls extension again so I don’t have to hop over to Kiwi for that.
Only a very small set of them though, and their functionality would likely be limited. Hopefully non-webkit browsers will come to ios soon, with proper desktop addons, following the eu pressuring them into allowing sideloading.
The user’s point still stands. He was offering an exception if you don’t want to wait on FF or Apple to change something for FF. Quit being smug aka an asshole.
I don’t care what others are saying, but I’ve never heard of this browser and I’m definitely going to give it a try. Wish I knew about this one sooner.
Mobile FF is already awesome with UBlock Origin and YT background playback extensions. I wish to install an auto redirect extension. (Twitter to Nitter) I know it is doable on beta w/ extensions etc. but I want to see them on normal Firefox.
I mean mainly allowing usage of user installed certificates required by mTLS,or at least that’s my use case. My company requires this in order to get access to company resources or better yet governments also require it for their online services.
i miss(ed) exactly two things on iOS: a proper imageboard reader (fixed, there are now chance and janchan) and stand alone firefox, wich is now just a matter of time.
I don’t see how they would, since ios Firefox doesn’t use the same rendering engine it uses on other platforms, Gecko. Instead it has to use Safari, just like any other browser on there.
Duplicating support for all existing extensions would be pretty much impossible if you don’t control the rendering engine.
this. they simply have to port the version they're developing for android now and we're golden. i guess it might find it's way on non-eu-devices by community builds and testflight.
Yeah it’ll be a big task nonetheless. Firefox for Android needed gecko components to be ready to make use of gecko view, their rendering “engine”. iOS may be need its own version of gecko view, at least the bindings for it, as well as a new set of components for all the UI elements a full fledged browser may need.
I heard about allowing alternative app stores, but I’m not sure if that also removes the browser engine restrictions. (would make sense though, from an anti-monopoly pov)
The restriction is from App Store, and bypassing it removes that hurdle. Microsoft faced the same issue when they were trying to launch their cloud streaming service within their app, not because they technically couldn’t, but because Apple wouldn’t let them to.
Add comment