Author: Hartley Charlton
According to The Register, developers who want to develop browsers for iOS with third-party engines can only test their applications on devices physically located in the EU.
This rule creates a significant barrier for developers outside the EU, who are now limited to using simulators instead of real devices to test their browsers. This limitation complicates the development and support of browsers with alternative engines, since on-device testing is necessary for accurate performance assessment and troubleshooting. Apple's previous policy, which remains in effect in other regions of the world, requires the use of WebKit for all iOS and iPadOS browsers, effectively turning every browser on those platforms into a variant of Safari.
Under the Digital Markets Act (DMA), Apple was appointed as an intermediary in the European Union, which forced the company to make changes to its policies. With the release of iOS 17.4, Apple began allowing the use of alternative browser engines in the EU. However, it has now emerged that testing of browsers with third-party engines is strictly tied to the EU, potentially limiting the ability of developers around the world to resolve security issues or effectively implement updates.
Requirements are increasing. some practical concerns about the ability to support a separate EU browser. Some developers have noted that Apple's extensive list of terms and conditions makes it difficult to comply with them, but at the same time ensures that the browser remains competitive and secure.
The European Commission has launched an investigation into Apple's compliance with the DMA, focusing on the restrictive nature of the latest changes. The investigation is aimed at determining whether Apple's requirements are intended to circumvent the spirit of DMA, making it more difficult for competitors to operate on a level playing field.
Tag: European Union[ 80 comments ]
