Why there are still no non-WebKit browsers on iOS
Apple’s tight control over iOS still effectively blocks full-featured browsers like Firefox or Chrome from using their own engines, even after EU rules forced Apple to nominally allow alternatives. Commenters examine how Apple’s regional restrictions, data-sharing limits, JIT entitlements, and separate-app requirements make non‑WebKit engines commercially unattractive, and debate whether the true drivers are security concerns, platform control, or protecting App Store and Safari revenue. The conversation also touches on broader worries about browser-engine monopolies, stalled web standards, and the trade-off between locked-down devices and user freedom.
Mozilla’s Challenges with Non-WebKit Firefox on iOS
- Apple requires non-WebKit browsers to be separate, region-limited SKUs (EU/Japan), so Mozilla cannot just “upgrade” existing Firefox; it would mean a full in-place migration of users and data between apps.
- Apple also forbids automatic state sharing (bookmarks, passwords, cookies) between the WebKit and non-WebKit Firefox apps without explicit user consent, making migration harder and UX worse.
- Some commenters doubt this is the real blocker, arguing Mozilla could still ship and see how it performs; others stress it doubles support complexity and fragments users.
Apple’s Rules for Alternative Browser Engines
- Alternative engines must comply with strict, often vague requirements (e.g., “memory-safe” languages, fast vulnerability fixes). Some note Apple itself may not fully meet similar standards.
- Engines must target only EU/Japan; development and testing must simulate those regions.
- Apple bars using normal app-group data sharing for these browsers, despite allowing it elsewhere.
- One requirement bans discussing non-public details of the program, which commenters see as silencing criticism.
Sideloading and Alternative App Stores
- Alternative app stores and sideloading exist but still require Apple-controlled entitlements (e.g., JIT), and Apple can refuse notarization (example: emulator apps).
- Some say you can publish without review via third-party stores; others reply Apple can still veto, so it’s not true freedom.
Apple’s Motivations: Money, Control, or Security?
- Many argue the real driver is protecting App Store revenue and the Google search deal, and weakening PWAs that could bypass the store.
- Others frame it as control over the platform and user experience.
- A minority argue it’s genuinely about security: JIT and large engines widen the attack surface, and iOS’s model relies on pre-validated code. Critics counter Safari is slow to update and not obviously safer.
Web Standards, PWAs, and Browser Monopoly Concerns
- Several claim Apple uses its iOS engine monopoly and W3C influence to block or delay APIs (WebBluetooth, WebSerial, WebUSB, richer PWA features) that could rival native apps.
- Others say many such APIs are Google-driven, privacy-hostile, or not widely needed, and note Safari scores competitively on some PWA capability tests.
- There is broad worry about Chrome/Chromium dominance; some see iOS’s WebKit lock-in as a necessary counterweight, others insist Apple could keep Safari default without banning engines.
Existing Non-WebKit Browsers and Practicality
- Gecko- and Chromium-based browsers (e.g., Reynard, Blinker-Fluid) exist via sideloading but lack notarization and JIT, so performance and polish lag.
- A few argue demand is low: most users won’t switch or migrate data, so the economics for full ports are poor.
Regulatory and Legal Aspects
- Commenters note EU rules nominally forced Apple to allow alternative engines, but the implementation is seen as hostile and designed to minimize real impact.
- Some mention ongoing or past antitrust actions in the US and EU, and call for stronger enforcement and fines; others ask what clear legal violation exists if users can choose Android instead.
Security vs Freedom / User Preference Split
- One camp wants a system-wide “let me install anything” toggle and sees current rules as anti-competitive.
- Another camp explicitly wants locked-down devices for themselves and family (e.g., elderly users), and would oppose such a toggle even if optional, fearing social engineering and misuse.