What I really want is to use chrome for PWAs and something that is essentially Firefox reader mode for actual web documents.
But if you kill them, by zapping with ublock or using another extension or bookmarklet, the performance is instantly a lot closer to something like the Chrome or Brave apps
It has been like this since Fenix launched, so at this point it makes me need to assume that it's some sort of fundamental limitation of their architecture. It is rather unfortunate.
The rest of the debate is just about the UX, really.
The latest incarnation... well it can choke on YouTube videos once in a while and you have to force kill it. And it does eat more battery than Chromium browsers.
But the current state is the first time I've found Firefox mobile version usable as a daily driver.
Maybe it's just phones have caught up - I'm on a Pixel 7.
But the point stands: vanilla FF mobile is now good-enough-for-me, and extensions make it wonderful.
Nothing else is really relevant to me on mobile.
It was the easiest browser option with adblock, which pretty much sealed the deal for me
I have not tested battery life, but it is acceptable to me, as is most of the performance.
I can confirm the full-screen video bug - I just tried watching a video on the New York Times site, and full-screening with Firefox is completely hosed, where Chrome works fine. I have Decentraleyes and uBlock installed as addons.
I have used add-ons with it for the past years. The ones you really need, like uBlock Origin, have always been there.
My experience is decidedly the opposite, and the single reason for that is uBlock Origin. The principal way to make websites load fast is to make them load less garbage. Fast browser engine is nice but not even close to proper content blocking (e.g. uBlock's JS defusers or DOM rules).
But extension capability is great overall. For example, you don't like how HN styles downvoted comments in unreadable light grey on light grey? Just add a user CSS extension and use this filter:
.c5a, .c73, .c82, .c88, .c9c, .cae, .cbe, .cce, .cdd { color: #222; font-style: italic; }I have no idea what you are talking about. I've been using Firefox and Firefox Focus for years and if anything it's always been fast and ultra reliable.
Around the same time as the extensions support was disabled, they removed a lot of features I liked and added some features and UI changes that still annoy me. It's a bit sad.
Man I have this, I have a very popular phone model, how can this not be fixed in years.
It was released as a preview in 2019 and has barely made appreciable strides since.
The team is so semi-competent that they have added and broken and disabled pull to refresh more than once now.
Add-ons have been on life support ever since they were introduced.
If I fullscreen a video, my browser minimizes.
Battery usage is abysmal.
Speed is noticably worse than any chromium fork.
Of course, I don't think I could do any better, but I'm not producing a browser, nor have I fired any engineers despite not having particularly reknown engineering chops as a company in recent memory.
This software is just terrible, especially because this failure isn't in a vacuum, it actually cements chromium as a monopoly of engineering competence.