A non-WebKit engine could spur deeper competition in web apps by enabling faster standards adoption, new developer tools, and alternative features, but it would raise concerns about fragmentation and cross-engine compatibility for developers and users.

Safari would face stronger competitive pressure if non-WebKit engines gain traction, pushing Apple to improve web compatibility, performance, privacy tools, and the developer experience to stay ahead.

The EU has created a regulated pathway called BrowserEngineKit that allows EU users on iOS 17.4+ and iPadOS 18+ to use alternative engines under entitlements with privacy and security safeguards, signaling a regional workaround rather than global openness.

The core issue is whether iPhone software can move beyond Apple’s engine without undermining the trust and security that underpin iOS’s value proposition.

The UK’s CMA is evaluating remedies that could remove or loosen the WebKit requirement, potentially amplifying pressure beyond the EU and risking regional fragmentation.

Apple’s likely strategy appears to be a regional compliance model with WebKit as the default worldwide, plus ongoing WebKit/Safari improvements to reduce regulatory pressure while regulators seek broader adoption of alternative engines.

Apple defends WebKit by citing security, privacy, battery life, and system integrity, arguing that opening the engine layer could raise risks and complexity for users.

EU and UK regulators are pressuring Apple to allow alternative browser engines or entitlements for non-WebKit engines to comply with the Digital Markets Act and competition investigations.

Historically, WebKit’s dominance on iPhone limits deeper engine-level competition, affecting features like JavaScript behavior, web apps, and performance.

The evolution of web apps and AI-enabled features in browsers is central; alternative engines could accelerate these capabilities, influencing privacy and user experience, even as Apple emphasizes on-device AI and privacy.