The final push to start using Firefox over Chrome on Android might finally be thanks to the enormous selection of add-ons (Firefox’s version of extensions) coming out next month. Chrome doesn’t offer native support for extensions in its mobile app. Also, better security.
I can’t. I’m already using Firefox.
When will management of site permissions like js and cookies and management of site data separatly will arrive?
Will switch that day!
Been using focus as my default for years, and Firefox for main stuff for years. Works fine for me and ublock is a must for me so…
IF FF ever implement support for tabs on tablets I might consider using it.
I only use phone and tablet and to use a glorified phone app on a tablet is not a great experience. Almost every other browser in existence supports tags for larger screens.
Until FF fixes this it doesn’t matter how many extensions they allow in the browser I’m out.
With the things that are going on with Google right now, it’s the right move to just switch to Firefox
Ublock, AdNauseum, Privacy Badger, oh my! All on Mobile phones!
I have issues with it. Some pages and apps don’t work well on Firefox. Rendering is off : alignments, some apps don’t even work. I will be switching away.
Just think, all those extensions where already here once. They just kicked it. I will never comprehend why.
Because Firefox for Android was slow as molasses… People keep complaining about the kissing extensions but Firefox was hella slow on android and the new Browser was drastically better. The only way to compete with Chrome was a rewrite. They still enabled individual extensions, the most popular. I, for one, am glad they took this route. We’re much better off today.
I just swapped off of it, Firefox has been buggy for me, no matter which fork I use, it’s been slow too. I recently just migrated to fulgris
I would use Firefox on Android but I’m waiting until the security is on par with Chromium such as having internal sandboxing and site isolation.
Also since Firefox doesn’t have a WebView implementation, it has to be used with the Chromium based one so it doesn’t make sense for me to use two browser engines.
I made a similar comment on this article in [email protected] - for anyone who is blindly downvoting thinking this is some Google psyop, this is the explanation from GrapheneOS (who fortunately provide their own de-googled chromium-based browser Vanadium):
Avoid Gecko-based browsers like Firefox as they’re currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn’t have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox’s sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn’t happening for their Android browser yet.
Samsung internet rocks and you can’t tell me otherwise.
Tracks u just as much as chrome
Nah
