On mobile Chrome does not support extensions while Firefox does. Recently on acquiring a new phone I used Chrome for a few days -- I had entirely forgotten how terrible the user-experience is without UBlock!
I always suspected the reason we never got extensions in mobile Chrome is that they didn't want the ad blockers. I wasn't aware that Firefox mobile started supporting them. Going to give it a try.
It's been assigned to some unknown person since 2015.
Though I'm not so sure the reason for it's delay in coming to Android isn't technical rather than organizational.
Brave for Android is based off of Chromium and it didn't have extensions either.
It sounds like the way extension APIs were initially implemented didn't lend itself to a Android port.
"We never had the Android version compiling with extension support in the first place - in our early development internally, we hacked/commented/disabled random parts of extension code just to get the binary to compile, and we later tidied this up to disable extensions in a neater way to save binary size. So, you are basically talking about actually implementing extension support for android from scratch, including adding every thing that extensions require but aren't currently implemented for Android. This isn't likely to be especially easy. " - https://groups.google.com/a/chromium.org/forum/m/#!topic/chr...
Though I don't understand why since Firefox mobile extensions are based off a similarly designed system (Jetpack) to Chromes.
It seems that if nothing else they could create a new API for extensions on Android.
> Though I don't understand why since Firefox mobile extensions are based off a similarly designed system (Jetpack) to Chromes.
Moreover, Mozilla is currently actually switching to an extended version of Chrome's extension API (which Mozilla calls "WebExtensions"). They had no problem implementing that on Android Firefox. Obviously, yes, there are APIs that just don't make sense on a mobile browser, but you have a well-defined API, so just blacklist extensions that require these APIs.
What app store does that other than Apple's? And a rule like that doesn't allow full web browsers so it's unrelated to the question of whether full web browsers have extensions.
The top 5 mobile browsers all allow ad blockers except Chrome. Samsung Internet which is based on the same chromium engine as chrome has had a similar ad block model as Safari for over 1 year now (and is the default browser on Samsung Galaxy devices - https://medium.com/samsung-internet-dev/think-you-know-the-t... )
Yes, the Samsung Internet application is recently (early 2017) available on Nexus devices as well. It's actually a great browser—Chromium under the hood, but supports content blockers, and is much smoother than Chrome itself. I've really enjoyed using it.
Also, disable javascript by default. It's really easy to turn it on per-site using the brave button in the toolbar.
The single best improvement I've made to my mobile browsing experience in years wasn't getting a new faster phone, it was installing Brave and disabling javascript.
And if someone's too lazy to install an add-on or on an unfamiliar computer, disabling Javascript is a simple as going to about:config, typing in "java", and double-clicking "javascript.enabled" to set it to false.
use firefox with the noScript (cross fingers to have uMatrix on mobile soon!)
then use your 10 top websites with whitelisted javascript access on firefox mobile, and full javascript on chrome and came back to say which one was faster.
Oh yes, my biggest pain is that Firefox can't replace the webview browser, so I still get tracked and shown ads if I use the Google app or any other app with the in-app webview browser.
