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.
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…
Ublock is absolutely a must.
Page on Firefox with unlock: 6 sentence news article.
Same page on chrome: video in the corner, popup blocking 30% of the screen, flashing ads every second sentence, halfway through there’s another popup asking you to log in.
Like wtf, people live like this?
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.
If treestyletabs worked on mobile that would work great. Just make the tabs bigger. Then again I think the UI is totally different on mobile so I feel the pain.
I have been using firefox on a phone since 2014 at least. I particularly like I can just go “send this tab to my PC” and it’ll just be there without bothering with bookmarks, note apps, emails to myself or such.
I once had a text file on a VPS I would ssh on my phone to and paste links into. Blah.
Completely agree. The tablet experience licks balls.
Tabs are needed, and god knows what it thinks its doing when you tell it to load the desktop version of a site. Apparently it thinks I clicked a button saying “embeggen all elements and waste screen space pls”…
Enjoy it on phone, mind.
loading the desktop version of a sits is not Firefox’s fault. It depends on the web devs.
Works fine on other browsers though. Not techy enough to say if your wrong or right, but the experience I have on a Tab s8 ultra is that ‘desktop’ versions are all zoomed in looking on FF.
I agree, on the phone it’s a great app.
My problem is that as I only use tablet and phone it doesn’t make sense to use two different browsers so until it’s changed Vivaldi it is.
Yep, same-zees. Big-time chrome user, switched on desktop and mobile to Firefox. As Google is being foolish twist these days.
Ublock, AdNauseum, Privacy Badger, oh my! All on Mobile phones!
Its possible for a long time, but hidden away.
When will management of site permissions like js and cookies and management of site data separatly will arrive?
Will switch that day!
Only gripe I’m having with Firefox on Android is the battery usage, which is quite awful unfortunately when compared to other browsers
I use Firefox on Android exclusively. Having ublock for youtube on my phone is great… But since updating to Android 13 watching full-screen video in FF has been an issue. Usually it requires that I restart the app to work.
With the things that are going on with Google right now, it’s the right move to just switch to Firefox
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
Been using FF on almy devices for over a year now. Best.Browser.Ever.
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 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.
Does anyone else have the problem that scrolling on a page becomes kinda laggy when there are more than usual elements on a webpage? For example, some website for streaming series. As soon as I scroll down where a lot of small buttons with episode numbers on them are rendered, Firefox on Android becomes noticeably laggy for me.
Other than that I really like it but that little problem annoys the hell out of me.
Yes it does lag much more than chrome, even on S23U. Even with noscript enabled, actually. I am trying to get used to it for the last few weeks cause goddam noscript makes internet a better place.
Which websites? Can you share some examples?
Try AniWatch for example and slowly scroll across the episode list.
I tried it. It appears to be an optimization issue. Firefox struggles a bit for some reason but not Chrome. Probably can be reported on the fenix repo for Firefox.
Confirmed laggy for me running Fennec on Android 13 on my S21.
I’ve encountered this laggy scrolling on other websites as well since switching to FF ~4 months ago.
Chromium based browsers on Android always have been more snappy than FF. That said I have primarily used FF for around a year and it is alright. Whenever something does not behave well, I use Vivaldi.
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.
