Apple’s quarterly profit performance was strong, but Open Network Advocacy stated that the company’s financial success was at the expense of iPhone user choice. The organization believes that, despite strong regulatory pressure in some areas, the continued restrictions imposed by apples on iOS browsers hinder and limit competition and have a negative impact on innovation. The European Union had explicitly addressed the anti-competitive behaviour of apples, but the company had responded only at a minimum.

Advocates stated that apple rules undermined web innovation and locked iPhone users in the Safari browser. The EU Digital Markets Act (DMA) forced apples to allow third-party browser engines in iOS 17.4. To be sure, Apple had done enough to deal with the blame rather than really giving users more choice. Outside the EU, iPhone users are still waiting for a browser that is not based on the Webkit kernel. Even within the European Union, Apple ‘ s response to the allegations appears to be superficial and fraught with obstacles, and developers face new challenges and constraints. Third-party developers and companies found it extremely difficult to create browsers other than the Webkit kernel, as apples made the process quite complex.

The organization further alleged that apples were deliberately designed to protect App Store ‘ s source of income by limiting the ability and attractiveness of web applications. In addition, this means that there will be no rivals who can outperform Safari in terms of performance and functionality. Ultimately, this stifles innovation and results in a large number of applications of similarity. The EU considered this illegal and stated that apples must allow third-party browser companies to compete freely and allow them to use their own browser engines. Apples have been partially compliant, which has prompted Google and Mozilla to begin developing web browser versions using their own engine (not WebKit). However, according to Open Web Advocacy, 15 months later, there is still no third-party browser based on a self-defined web engine available. Why? Apple cleverly places multiple barriers at the legal, technical, practical and marketing levels for developers, limiting their possibilities to launch their own version of the browser.

Apple rules and technical restrictions prevented other browser providers from successfully providing their own engines to users in the EU. At the recent DMA workshop, Apple claimed that it was unclear why no browser supplier had transplanted its engine to iOS in the past 15 months. But the reality is that apples know the obstacles and choose not to remove them. The organization stated that apples placed these barriers in order to continue to derive economic benefits from Safari. Safari, the most profitable apple product in history, contributes between 14 and 16 per cent of its annual operating profits and generates $20 billion annually through Google Search Engine agreements. The company will lose $200 million per year for every 1 per cent of its market share of the browser.

Apple denied these allegations, declared that it had complied with the new regulations and stated that it was unclear why the third-party browser company had not introduced products based on a free engine. It remains to be seen how apples will move forward on this matter, but, on the basis of the information available, their potential for substantial change is minimal.

