Asus To Integrate Adblock Plus Into Mobile Browser
David Murphy / PC Magazine :
Context & Ripple Effects
Adblock Plus spent 2015 building its own distribution: an Adblock Browser built on Firefox for Android in May, then a standalone free browser on Android and iOS in September — both of which required users to seek the app out and switch away from their default browser. The Asus deal changes that math entirely.
First-order effects
- Adblock Plus goes from an app users must download to a feature activated by default in Asus' proprietary browser shipping on its mobile devices from early 2016, giving the blocker OEM-scale distribution it never had.
- Publishers and ad networks lose ad inventory on every Asus device out of the box, since no user action is needed to suppress ads.
Second-order effects
- Samsung's February update adding support for third-party ad-blocking plugins in its own Android browser confirms the pattern — once one major handset maker ships blocking by default or near-default, rivals face pressure to match the feature or explain why they didn't.
- The deal pressures Google's position: its Android ecosystem monetizes through search and display advertising, so OEM-level blocking on its partners' devices strikes at the revenue model without any policy change on Google's part.
Third-order effects
- Ad blocking stops being a niche consumer choice and becomes a platform-level bargaining chip between device makers, blocker vendors, and the ad industry — pushing publishers toward formats and deals (such as acceptable-ads arrangements) that can survive a default-blocked browser.
- If OEM integration becomes standard, browser choice on Android increasingly determines whose ads get seen, shifting power in mobile advertising from networks toward whoever controls the default browser.
The trend: Mobile ad blocking is moving from user-installed apps to preinstalled, default-on browser features via OEM partnerships, with Samsung's follow-on plugin support showing the shift spreading across handset makers.