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!
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.
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.
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.
[1] https://addons.mozilla.org/en-US/android/addon/toggle-javasc...
Brave is a Chrome fork so for those of us who prefer Chrome it's a better option (for now anyway).
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.