Google Reverses Its Choice To Ban Advert Blocking Apps From The Google Play Retailer

Google Reverses Its Decision To Ban Ad Blocking Apps From The Google Play Store

Google seems to have reversed its earlier determination to ban advert blockers from the Google Play retailer – a transfer which had seen the corporate pulling apps like Adblock Quick and stalling the updates for others, like Crystal’s advert blocker. Now, following an attraction from Rocketship, the builders behind Adblock Quick, Google has re-accepted and republished its app to Google Play.

The choice represents a change in course for Google, relating to its place on what kind of apps the corporate will permit in its app retailer for Android units.

From a supply with information of the state of affairs, TechCrunch discovered on the time of the unique determination that Google had deliberate to solely help cellular browsers that would block advertisements – together with these with constructed-in advert-blocking options, just like the Adblock Plus browser, in addition to people who supported advert blocking by way of extensions, as with Firefox, Javelin, and Dolphin browsers.

Nevertheless, Google had determined that standalone advert blocking apps distributed by way of APKs, like Crystal and Adblock Quick, wouldn’t be permitted underneath its new tips.

These apps and others had emerged following Samsung’s introduction of advert blocking help inside its personal cellular net browser in early February. The function labored so much like how Apple’s Safari helps advert blocking. That’s, third-social gathering builders can benefit from Samsung’s new Content material Blocker API which permits them to construct apps that work the browser to dam advertisements and different undesirable content material that may decelerate net pages, like trackers.

Google Reverses Its Decision To Ban Ad Blocking Apps From The Google Play Store

However there was already some indication that Google might have been debating its choice forward of Adblock Quick’s reinstatement, as Google’s coverage was being inconsistently utilized.

Whereas Adblock Quick was pulled, Crystal was merely slowed down, for instance – Google blocked its app replace from going via, citing the identical “violation” of its Android Developer Distribution Settlement as the rationale.

In Part four.four, the corporate informs third-social gathering builders that they can’t intrude with “the units, servers, networks, or different properties or providers of any third-social gathering together with, however not restricted to, Android customers, Google or any cellular community operator.”

As no additional steerage was provided, affected builders stated they perceive Google’s request to imply they need to not intrude with Samsung’s net browser.

That call clearly didn’t make sense as Samsung’s launch of its advert blocking API indicated that was precisely what the corporate needed third-get together builders to do.

Rocketship says it submitted an attraction final Monday – the day its app replace was rejected  – which was earlier than the app itself was pulled from the shop on Tuesday.

As we speak, Rocketship explains what occurred since. The corporate says it acquired an e-mail on Friday noting that Google had accepted its attraction, then the app was republished this morning.

Along with being again on Google Play, Rocketship was additionally capable of replace the app to model, which now extends help as much as Android and clarifies the onboarding expertise for these customers who didn’t but have Samsung’s net browser put in.

As Google flip-flopped on its determination, different advert blockers makers remained kind of untouched by the shifting coverage. As an example, Adblock Plus, which launched a model of its advert blocker for Samsung Browser, tells us they by no means heard from Google nor had their app pulled.

Crystal additionally stays on-line and can possible be capable of push by means of updates going ahead, as properly. (We’ve reached out to verify the pending replace is ready to go stay.)

Google was not instantly out there for remark.