BrowserEngineKit – Apple Developer Documentation

Original Article ↗ Hacker News Discussion ↗

Apple’s new BrowserEngineKit framework will, for the first time, let third‑party browser engines like Chromium and Gecko run natively on iOS—but only for users in the EU, where the Digital Markets Act is forcing Apple to loosen its platform restrictions. Commenters weigh the benefits of true Firefox- and Chrome-based browsers with full extension support against concerns over increased attack surface, tracking, and the likelihood of further cementing Chromium’s dominance over web standards. Many also question how much ordinary users will care, noting that browser choice is often driven more by defaults and corporate power than by technical quality.

Scope of Apple’s BrowserEngineKit Change

  • Allows alternative browser engines on iOS, but EU-only and with strict conditions:
    • App must be EU-only, separate binary from WebKit-based version, and cannot have the default-browser entitlement.
    • Entitlement required; Apple can gate who ships an engine and impose privacy constraints (e.g., third‑party cookies off by default).
  • Some see the APIs as more capable and less petty than expected (JIT, multiprocess apparently possible).

Firefox, Extensions, and Existing Workarounds

  • Many are excited about “real” Firefox with its own engine and full extensions, especially for uBlock Origin.
  • Others note that Orion already supports many Chrome/Firefox extensions on iOS via WebKit, but with limitations (e.g., uBlock not fully working).
  • Doubts raised about whether Mozilla will invest heavily in an EU‑only iOS engine given recent cutbacks and prior abandoned ports.

Chromium Dominance vs Engine Diversity

  • Concern that this will push iOS toward Chromium, strengthening Google’s control over web standards and tracking.
  • Counterpoint: even an imperfect WebKit/Safari is useful as a non‑Chromium engine to limit Google’s unilateral power.
  • Some argue Safari’s development pace and opacity are so poor that a Chromium monoculture might be preferable in practice.

Security, “Walled Garden,” and User Choice

  • One side: opening iOS increases attack surface and benefits malware authors, trackers, and authoritarian regimes.
  • Other side: Android and desktop already allow multiple engines and stores and “look fine” for typical users; fears are seen as overblown.
  • Debate over whether this is truly “user choice”:
    • Users may be forced to follow developers into alternative stores or engines to access essential apps.
    • Some view regulatory intervention (DMA) as necessary to counter platform power; others say people buy iOS precisely for tight control.

Advertising, Tracking, and PWAs

  • Several expect this to be a “huge win” for ad tech:
    • Fewer Safari users means less Intelligent Tracking Prevention and longer‑lived cookies.
  • Others note possible upsides: better PWA support and pressure on Apple to improve Safari (e.g., Web Bluetooth).

Practicalities and Open Questions

  • Only EU‑resident iOS users qualify; switching Apple ID region is possible but painful and may cost access to some apps.
  • Questions remain about:
    • How quickly Chrome/Firefox can ship full engines.
    • Whether captive portal and system web views will respect alternative browsers.
    • Whether Web Bluetooth and similar APIs will appear via third‑party engines.