As per comment, we might pull this back into a Battery saving story after MVP, however it should land for MVP as an individual feature.
The absence of Ad-blocker is a fatal matter for us to enjoy Firefox-preview.
Shouldn't this better be left to add-ons like uBlock and AdBlock? With support for plugins hopefully coming, what is the reason for implementing this in the browser itself?
Indeed, it seems to me that when #574 is implemented it also automatically resolves this userstory.
The reason for this to ship in Firefox itself, instead of an add-on is that many users do not know about add-on support.
Most does not even know what an add-on is. They just install the browser and get on with it.
This should be in Firefox itself, if you ask me!
Still, add-on support in Firefox Mobile, should be more marketed!!!
Extension support is a much larger story than adblocking. Native adblocking is a quick win, especially considering that many potential beta testers could be holding out for this specific feature.
Is it really a good idea to push adblocking to a broader user base? If it's built into the browser (especially if enabled by default), it could cause problems in the longterm.
Adblocking is only viable because the majority of users don't know or bother with it. If they did, then websites would start using ads that are more difficult to block or even shift their revenue models.
Extension support would be a greater win. But the browser should probably have a basic blocking role. Offer tracking protection like the desktop browser and default deny anything known to be serving malicious code (if there's some good metric for that), but for actual ad blocking leave that to extensions.
Brave browser demonstrated that people are willing to jump on a new browser for the sake of "easy to use privacy and ad-blocking". It's a shame they did this on the Chrome engine, giving Google ever more power over the internet.
The sad truth is, that on mobile you want an as hassle-free experience as possible.
I can't teach every person in my entourage how to install plugins and what they are, so I just let them use brave in the meantime.
Fenix seems to have the potential to change this. At least make it optional.
@ChriKn Well, that's true. For my 2¢, I think if extensions were supported, having preinstalled uBlock or something like that (that can be removed of course) would probably be an easy win without having to re-engineer the same thing. But I'm just a "passerby" commenter :laughing:.
having preinstalled uBlock or something like that
There is not only one ad blocker for Firefox. Preinstalling an arbitrary ad blocker would be really bad for the competition of ad blockers and therefore for the whole add-on ecosystem of Firefox.
That's true, but wouldn't the same hold for implementing a built-in ad blocker?
Of course you can argue with the question: _Why should users install an ad blocker if Fenix already has ad blocking capabilities?_
But for me there is one important difference: add-ons can always make things different. They can provide more features because a built-in feature will probably have a stronger focus on the average user and don't include all features you can think of. There is a fair competion because no add-on developer is preferred. This won't hurt the add-on ecosystem (well, the ad blocking add-ons will probably have fewer users if an ad blocker is already integrated, but it's the same situation for all third party developers at least). But preinstalling an add-on means making a choice for one third party developer and against all competitors. With uBlock (or any other ad blocker) already included there is probably no point for users to install an ad blocker from one of the add-on's competitors.
a built-in feature will probably have a stronger focus on the average user and don't include all features you can think of
I agree...
There is a fair competion because no add-on developer is preferred.
I disagree, Mozilla would be preferred...
But overall, I probably agree with you that it would hurt competition more to select a 3rd party developer instead of a 1st party one.
Solution is easy, give a good third party option that can be disabled and replaced by a third-party one of the desire arises.
(The problem is probably that Google (the n°1 money source of Mozilla) would lose its mind/it is part of their agreement...)
uBlock origin can be installed now so that should close this issue.
@ReekyMarko since when? Is there a new version that hasn't hit the Play Store yet? I've got the latest Play Store version and neither uBlock Origin (the proper one) nor the top "uBlock" results say they're compatible (and can't be installed).
It was just updated a couple of hours ago in the Play Store. Installing from addons.mozilla.org does not work yet.
You should have at minimum Nightly 200204 18:00 (Build #20351804)
. Then you should have "Add-ons" under Settings -> Advanced and you can install uBlock origin from there.
Here is some discussion on the release: https://redd.it/eyvgtk
This has hit nightly, meaning it is still not released to the regular firefox preview and under test.
Oh I just assumed everyone here is running Nightly. Might be that @jgoguen is running the stable version.
Most helpful comment
Shouldn't this better be left to add-ons like uBlock and AdBlock? With support for plugins hopefully coming, what is the reason for implementing this in the browser itself?