Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Google Chrome IT

Google Testing a Version of Chrome for Android With Extensions Support (androidauthority.com) 10

Google is developing a version of Chrome for Android that supports browser extensions, a feature long absent from mobile versions, AndroidAuthority reports. The report adds: Specifically, the company is experimenting with "desktop" builds of Chrome for Android. These "desktop" builds are currently intended for Chromebooks as they transition to use more parts of Android, but there's hope the work will benefit mobile devices, too.
This discussion has been archived. No new comments can be posted.

Google Testing a Version of Chrome for Android With Extensions Support

Comments Filter:
  • Ad blocking (Score:5, Insightful)

    by bbcisdabomb ( 863966 ) on Monday October 07, 2024 @01:16PM (#64846205)

    What's the point of having extensions on mobile if I can't use uBlock or the like? They're really just going to take out support for the really useful stuff and shove it out to phones?

    • Re:Ad blocking (Score:5, Insightful)

      by bartoku ( 922448 ) on Monday October 07, 2024 @01:43PM (#64846253)

      I would recommend Firefox for Android for using uBlock, and only using Chrome to access Google web apps.
      I enjoy customizing Gmail and other Google Web Apps through extensions on Chrome desktop, so this will be great on mobile for Chrome.

      • by AmiMoJo ( 196126 )

        I've been testing Firefox for Android for years. uBlock is unfortunately a battery killer, probably due to the fact that Firefox's filtering and regular expression handling are done in Javascript. Chrome does them with C++ code, although I expect that uBlock is probably still going to be quite heavy on your battery.

        I've been testing out uBlock Lite for Firefox, and it barely touches the battery at all. It blocks about 80% of the stuff that the full-fat version does, which is still vastly better than DNS blo

    • by Himmy32 ( 650060 )

      The article explicitly calls out that this announcement isn't for mobile (ChromeOS shares the code base) and they also calls out that the suspected reason of no extensions for mobile is adblocking. From the article:

      • Google finally appears to be working on a version of Chrome for Android that supports browser extensions, but there’s a catch: it likely won’t be available for mobile devices.

      • That’s because Google decided way back to not add extension support to mobile versions of Chrome, likely to limit the number of people installing Chrome extensions to block ads on their Android phones.

      • by AmiMoJo ( 196126 )

        It's probably not adblocking. If Google wanted to kill that they would have done it years ago, and e.g. by not going to all the effort of creating a brand new API to let Manifest V3 extensions block ads.

        It's because of UI issues. Most extensions are designed for desktop, and their UIs break on mobile. Firefox had the same problem, and it took years for extensions to get updated with mobile compatible UIs, and most of them are still quite rough around the edges.

    • Re:Ad blocking (Score:5, Interesting)

      by narcc ( 412956 ) on Monday October 07, 2024 @03:32PM (#64846503) Journal

      This is yet another reason why FireFox is important for the web. uBlock works just fine on mobile and will continue to do so. If you haven't done so already, make the switch. It's liberating.

      • by _merlin ( 160982 )

        Hell, even the Samsung Internet browser provides specific support for ad-blocking extensions. Chrome is the worst browser.

      • by AmiMoJo ( 196126 )

        I wouldn't say uBlock works "fine" on mobile. It's very heavy on battery, partly because Firefox's filtering API code is written in Javascript so performance is quite poor.

        By contrast the uBlock Lite version, which uses a newer C++ filtering engine, barely touches the battery. I speculated that that was the reason for Manifest V3 introducing a new filtering API, and it looks like I was right.

  • by FudRucker ( 866063 ) on Monday October 07, 2024 @02:06PM (#64846289)
    Chrome on android has been a neglected piece of crapware for so long that it sits unused and disabled, under the hood the browser engine webview seems to be okay so i am always on the lookout for alternative lightweight frontends that use it like Berry browser is a good one, Tiny browser is the best of the bare-bones browsers, but lately i been using Vivaldi and more recently Firefox, okay back to Chrome on android = I think it needs a complete rewrite, and get rid of the sponcered links! google makes enough money that they should not be shoving unwanted links into other people's browser experience
  • Kiwi browser [kiwibrowser.com] has done this for a while. I've used it for a while and It's pretty stable, even ublock works fine. Some things are a little clunky like trying to use dev tools, but it's far superior to Chrome on Android.

Force needed to accelerate 2.2lbs of cookies = 1 Fig-newton to 1 meter per second

Working...