Mozilla exec at internal event: “we're going to get Firefox on iOS”
Firefox Could Soon Come To iOS — For a year now, Mozilla has categorically stated that it wouldn't release a version of Firefox for iOS because Apple won't let it use its own web engine on its platform.
Context & Ripple Effects
Mozilla spent years refusing to ship Firefox on iPhone and iPad, arguing that Apple's ban on third-party browser engines made any iOS port a hollowed-out product — a stance it stated publicly in early 2013. This internal-event reversal marks the moment that principle gave way to distribution reality: with Firefox's desktop share eroding, Mozilla could no longer afford to cede the entire mobile browsing market to rivals who had already swallowed the same compromise.
First-order effects
- Mozilla commits to building an iOS Firefox despite its own long-standing objection — meaning the app will have to run on Apple's WebKit engine rather than Mozilla's own Gecko, the exact trade-off it previously called disqualifying.
- iPhone and iPad users gain access to Firefox's accounts, sync, and reading features for the first time, while Mozilla's leadership signals the decision internally before any public product announcement.
Second-order effects
- The move completes a pattern among engine makers: if Chrome accepted a WebKit-based iOS build, Firefox staying out stopped being a differentiator and started being self-marginalization, pushing every remaining holdout toward the same capitulation.
- Apple faces growing pressure from browser vendors who comply with its rules only under protest — pressure that later resurfaces when Mozilla begins exploratory work on a Gecko-based iOS browser contingent on Apple dropping the WebKit requirement.
Third-order effects
- If the pattern holds, third-party browsers on iOS become permanent 'shell' products — branded UIs over a mandated engine — until regulation or platform-policy change forces Apple to open its engine layer, which is precisely the fight Mozilla re-enters years later by criticizing BrowserEngineKit restrictions.
- For Mozilla specifically, the episode foreshadows its strategic drift: a nonprofit built on an independent engine increasingly dependent on platforms it doesn't control, culminating in the broader turnaround effort around the 2015 marketing and product push to arrest its decline.
The trend: Platform gatekeepers' engine mandates are steadily forcing independent browser makers to choose between principled absence and compromised presence — a tension that regulation is only beginning to unwind.