Japan to Allow Non-WebKit Browsers on iPhone by Law

Japan's New Law Will Allow Non-WebKit Browsers on iPhone

iPhone users in Japan are about to experience a major shift in mobile browsing. A new regulation, known as the Mobile Software Competition Act, mandates that Apple must support non-WebKit browsers on iPhone by the end of this year. Until now, Apple has only allowed browsers that rely on WebKit—the engine behind Safari. This limitation meant that popular alternatives like Chrome, Firefox, and Edge were merely different skins over Safari's engine on iOS. With Japan’s intervention, Apple will be legally required to support alternative engines like Chromium’s Blink and Firefox’s Gecko, giving users more freedom and developers more flexibility.

Image : Google

Why Non-WebKit Browsers on iPhone Matter

The move to enable non-WebKit browsers on iPhone is more than a legal technicality—it’s a fundamental change to how iOS operates. Apple has long argued that restricting third-party browsers to WebKit helps maintain security, privacy, and performance standards. However, critics and regulators argue that this limitation stifles innovation and unfairly blocks competition. Japan’s new law is designed to open the door for browser diversity, ensuring that developers can use their preferred rendering engines without facing restrictions. This will not only enhance user choice but also allow faster innovation in features, performance, and web standards.

By enforcing support for alternative browser engines, Japan is signaling a commitment to fair digital markets. For example, browsers built on Blink often support features and standards that WebKit does not, giving developers broader possibilities. Until now, iOS users were effectively cut off from the full experience of non-Safari browsers. With this legal change, iPhone users in Japan will be able to experience the same level of browser diversity as those on Android or desktop platforms.

What This Means for Apple and iOS Developers

With this regulation coming into effect by December 2025, Apple will need to revise its iOS policies and App Store review guidelines. Unlike its recent partial compliance in the EU, where technical and bureaucratic barriers still limit the use of non-WebKit browsers, Japan’s law takes a more aggressive stance. It explicitly bans "unreasonable technical restrictions" and forces Apple to implement a default browser selection screen in Safari. This means developers looking to launch browsers based on engines like Blink or Gecko should find fewer roadblocks moving forward.

The implications for iOS developers are significant. No longer tied to WebKit, browser creators can now offer distinct features, enhanced performance, and custom developer tools that weren't feasible under Apple’s previous constraints. This could lead to a surge in innovation within the App Store and potentially improve the user experience for millions. Moreover, companies that build in-app browsers for their services will gain more control over how content is rendered, which can affect everything from ads to streaming experiences.

Global Impact and the Future of Browser Choice on iPhone

Japan isn’t alone in challenging Apple’s browser policies. Similar pressures have emerged in the European Union under the Digital Markets Act, which led to some changes in iOS 17.4 and iPadOS 18. However, Japan's legislation is seen as stricter and more direct, potentially setting a precedent for other regions like the UK and even parts of North America. If this trend continues, Apple may be forced to standardize support for non-WebKit browsers on iPhone globally.

For users, this shift means more freedom to choose how they browse the web. For developers, it means greater creative control and the potential for higher-quality apps. For Apple, it means adjusting long-held policies that have helped define iOS’s closed ecosystem. Whether seen as a win for competition or a challenge to Apple’s control, Japan’s bold stance could reshape the mobile web landscape in 2025 and beyond.

Post a Comment

Previous Post Next Post