HN Debrief

Firefox for iOS now has a native adblocker

  • Privacy
  • Browsers
  • Mobile
  • Regulation
  • Business Models

Mozilla posted support docs for a new native ad blocker in Firefox for iOS. It blocks many ads and trackers at the network level using EasyList, but Mozilla explicitly says it does not block ads in search results or sponsored content on Firefox’s own home and new-tab surfaces. That caveat dominated the reaction. People read it as Mozilla drawing a revenue line rather than a technical one, and several pointed out that those search ads are exactly where scams and low-quality ads do the most damage.

If you use Firefox on iPhone, this is a real upgrade but not the end of the story. For the best blocking on iOS today, you still need to choose based on scope and trust: Firefox for in-browser convenience, or Safari-based blockers if you want broader coverage across web views and apps.

Discussion mood

Cautiously positive, with a lot of irritation layered on top. People liked getting built-in blocking in Firefox for iOS, but most of the energy went into complaining about the missing search-ad blocking, Apple’s restrictions on iOS browsers, and the fact that Safari-based blockers still do more across the system.

Key insights

  1. 01

    Safari blockers still win on coverage

    Safari-based blockers are stronger on iOS because they can use Apple’s Content Blocker APIs and reach many system web views, not just pages opened inside one browser. That is why people keep pairing tools like Wipr, Filtr, or AdGuard with Safari even if they trust uBlock more. Firefox’s new blocker improves Firefox itself, but it does not replace the broader blocking stack Apple exposes to Safari-centric apps.

    If your priority is fewer ads across the whole phone, test Safari-based blockers before standardizing on Firefox. If your priority is staying inside Firefox, accept that you are trading away some coverage for convenience.

      Attribution:
    • armadyl #1
    • Barbing #1
    • anon7000 #1
    • ronjouch #1
    • yesb #1
    • Forgeties79 #1
  2. 02

    uBlock Origin Lite is less crippled than many assume

    A lot of people still talk about uBlock Origin Lite as if Manifest V3 makes it barely useful. That picture is stale. Several comments noted that cosmetic filtering and scriptlet-based filtering do work in stronger modes, rule limits are often worked around by splitting lists, and the declarative design can reduce extension access to browsing data. The gap versus full uBlock Origin is real, but for ordinary mobile browsing the practical difference can be much smaller than the spec sheet suggests.

    Do not dismiss uBlock Origin Lite from the label alone. For a mobile deployment or a personal setup, test real pages you care about before assuming you need full desktop-style extension power.

      Attribution:
    • simcop2387 #1
    • kqp #1
    • gorhill #1
    • Asmod4n #1
    • snazz #1
  3. 03

    Firefox already had a hidden path through Focus

    Mozilla was not starting from zero on iOS ad blocking. Firefox Focus, called Klar in some markets, has long exposed blocking through Apple’s content-blocker system and can also help in Safari. That made this launch feel less like a breakthrough and more like Mozilla finally moving a useful capability into the main browser where regular users will actually find it.

    If you support iOS users, check whether they already know about Focus or Klar before treating this as a net-new category of protection. The operational change here is lower friction and better discoverability, not a brand-new technical capability.

      Attribution:
    • VCFundedGenYer #1
    • brightbeige #1
    • adityeah #1
  4. 04

    Apple policy still sets the ceiling

    The biggest limitation is not the filter list. It is Apple’s control over browser engines and distribution. Comments pointed out that Firefox add-ons on iOS are constrained because Mozilla cannot ship the same Gecko-based browser stack it uses elsewhere, and the alternative-engine path in the EU and Japan is wrapped in enough conditions that it has not opened the market in practice. That is why every iOS browser discussion keeps collapsing back into WebKit and Safari APIs.

    Treat iOS browser strategy as a platform-policy problem, not just a feature-roadmap problem. If your product depends on advanced browser capabilities, expect regional fragmentation and slower progress than on desktop or Android.

      Attribution:
    • TheDong #1
    • Nextgrid #1
    • Gareth321 #1
    • close04 #1
    • VCFundedGenYer #1

Against the grain

  1. 01

    Apple’s lock-in also checks Blink dominance

    A minority view held that Apple’s restrictions are not just anti-competitive damage. They also prevent Chromium and Blink from becoming the only browser engine that matters on mobile. Even if Apple’s motives are self-serving, this camp sees a forced WebKit presence as a rough counterweight to Google’s power over the web stack.

    If you care about browser-engine diversity, do not assume every move against Apple automatically improves the web. Watch for outcomes that simply swap one gatekeeper for another.

      Attribution:
    • zer0zzz #1
    • criddell #1
  2. 02

    Ad blocking solves symptoms, not web funding

    Some comments pushed past browser choice and argued that the harder problem is how publishers get paid once ads stop working. Micropayments and broader paid access got real interest, but people also noted the brutal economics. Most users resist even tiny charges, and subscriptions convert better than per-article fees. The point was not that ads are good. It was that better blockers do not by themselves create a replacement business model for the open web.

    If you run content or discovery products, do not read stronger ad blocking as only a UX story. Keep testing paid models now, because browser-level blocking keeps getting easier while the old ad bargain keeps weakening.

      Attribution:
    • Sha1rholder #1 #2
    • tensor #1
    • upboundspiral #1
    • Scaled #1

In plain english

Blink ↩
Google’s browser engine used by Chrome, Edge, Brave, and many other Chromium-based browsers.
cosmetic filtering ↩
Hiding or removing visible page elements like ad boxes or banners after a page loads.
EasyList ↩
A widely used community-maintained list of rules that ad blockers use to identify and block ads and trackers.
Gecko ↩
Mozilla’s browser engine, used by Firefox on desktop and Android but not generally allowed on iOS.
Manifest V3 ↩
A newer browser extension system from Google that restricts how blockers work and pushes them toward declarative rules.
uBlock Origin ↩
A browser extension that blocks ads, trackers, and unwanted page elements.
uBlock Origin Lite ↩
A lighter version of uBlock Origin built around newer browser extension limits, especially the declarative model used by Manifest V3.
WebKit ↩
Apple’s browser engine framework used to render web content on its platforms.

Reference links

iOS ad blockers and browser tools

uBlock Origin Lite technical details

Apple browser engine rules

Web economics and payment alternatives

  • Project Xanadu
    Mentioned in a conversation about micropayments as an alternative to ad-funded content
  • Cloudflare Pay
    Shared as a possible piece of infrastructure for micropayments