Adblock Plus launches Adblock Browser: Firefox for Android with built-in ad blocking
Adblock Plus today launched Adblock Browser for Android. Currently in beta, the company's first browser was created by taking the open source Firefox for Android and including Adblock Plus out-of-the-box.
Context & Ripple Effects
Adblock Plus has spent years as an extension users had to install themselves; Adblock Browser flips that by taking the open source Firefox for Android codebase and shipping the blocker switched on out of the box, giving the company its own distribution channel on the platform where [[entity:Firefox|Firefox]] itself struggled because default search settings disadvantaged it.
The launch kicked off a recognizable sequence over the following year: Asus moved to include and activate Adblock Plus by default in its proprietary mobile browser starting early 2016, Samsung added third-party ad-blocking plugin support to its own Android browser rather than building one in-house, and Opera answered with a native blocker in its stable release and Opera Mini for Android by mid-2016 — evidence the beta was the opening move in a broader land grab for the mobile blocking layer.
First-order effects
- Android users get ad blocking without hunting for or configuring an extension, and Adblock Plus gains a first-party browser that no longer depends on store listings or extension APIs it does not control.
- Mozilla's Firefox code reaches Android users under another company's brand, meaning Adblock Plus captures the relationship (and any associated revenue) on top of Mozilla's engine work.
Second-order effects
- Browser makers are forced to respond in kind — Opera shipped a built-in blocker across its stable and Mini channels within a year, turning ad blocking from a niche extension into a table-stakes browser feature.
- OEMs choose integration over development: Asus activates Adblock Plus by default in its shipping browser and Samsung opens its browser to third-party blockers, moving the decision about mobile ads from publishers to device makers.
Third-order effects
- If the OEM-default pattern holds, mobile ad inventory erodes structurally: blocking stops being an opt-in behavior of technical users and becomes the factory setting on shipped devices, pressuring publishers and ad networks to redesign formats around consent rather than volume.
- Browsers increasingly compete on how aggressively they block ads rather than rendering speed alone — a shift that eventually pulls platform owners like Google, whose revenue depends on those ads, into defending the status quo.
The trend: Mobile ad blocking is migrating from user-installed extensions to built-in defaults in browsers and OEM software, resetting who controls the mobile web's ad economics.