Why Apple Forced iOS Browsers to Use the WebKit Engine

Prior to the enforcement of the European Union's Digital Markets Act, Apple maintained a strict App Store policy requiring all third-party web browsers on iOS—such as Google Chrome and Mozilla Firefox—to run on its proprietary WebKit rendering engine. This article provides a straightforward examination of the reasons behind this long-standing requirement, covering Apple's official justifications regarding device security, user privacy, and battery efficiency, alongside the antitrust arguments that the rule was designed to protect App Store revenue and maintain ecosystem control.

The Reality of Third-Party Browsers on iOS

Under App Store Review Guideline 2.5.6, every browser on an iPhone or iPad had to use the WebKit framework. On desktop computers and Android devices, Chrome uses the Blink engine and Firefox uses the Gecko engine. However, on iOS, these browsers were essentially custom user interfaces wrapped around Apple’s Safari engine. They could offer their own bookmark syncing, password managers, and visual layouts, but the core technology rendering the web pages was identical to Safari.

Apple justified and maintained this restriction for several key reasons.

1. Centralized Security and Threat Mitigation

Web browsers are the primary entry point for malware and security exploits because they constantly download and execute untrusted code from the internet. Modern browser engines use Just-In-Time (JIT) compilation to run complex web applications quickly, a process that historically introduces significant security vulnerabilities.

By forcing all browsers to use WebKit, Apple created a single point of defense. If a critical vulnerability was discovered in the rendering engine, Apple could issue a single iOS update to patch Safari and every third-party browser simultaneously. If browsers were allowed to use their own engines, iOS users would be entirely dependent on third-party developers like Google or Mozilla to quickly find, patch, and submit updates for their specific engines, potentially leaving iPhones exposed to threats in the interim.

2. Privacy Enforcement

Apple heavily markets its devices on the premise of user privacy. By controlling the underlying browser engine, Apple could enforce system-wide privacy standards that third-party engines might otherwise bypass.

Through WebKit, Apple implemented Intelligent Tracking Prevention (ITP), which restricts advertisers from tracking users across different websites. If Google were allowed to use its Blink engine on iOS, it could theoretically configure Chrome to allow more invasive data collection and ad-tracking techniques that run counter to Apple's privacy framework.

3. Battery Life and Hardware Optimization

Apple designs both the hardware (A-series chips) and the software (iOS) for its mobile devices. WebKit was specifically engineered to work in tandem with Apple's custom silicon.

This tight integration allowed Apple to maximize performance while minimizing power consumption. Third-party engines, built to run across a vast array of different operating systems and hardware configurations, are not as specifically optimized for iOS. Apple argued that allowing alternative engines would lead to higher CPU usage, overheating, and faster battery drain, which users would ultimately blame on the iPhone hardware rather than the third-party browser app.

4. Ecosystem Control and App Store Revenue

While Apple cited security, privacy, and performance, regulators and competitors argued that the WebKit requirement was primarily a business strategy to protect the App Store monopoly.

Alternative engines, particularly Google's Blink, aggressively support advanced web standards that allow for Progressive Web Apps (PWAs). PWAs are websites that look, feel, and function just like native apps, capable of working offline and sending push notifications, all without needing to be downloaded from an app store.

By forcing all browsers to use WebKit, Apple alone dictated the pace at which web apps could evolve on iOS. By withholding features from WebKit that would make web apps viable alternatives to native apps, Apple ensured that developers had no choice but to build native iOS apps. This kept developers locked into the App Store ecosystem, allowing Apple to continue collecting its 15% to 30% commission on digital goods and subscriptions.