Apple won’t remove web apps from iOS after all. The iPhone maker had originally planned to do this as a middle finger to strict European regulations, but a threatened EU investigation into this response has caused Cupertino to change its mind.

“If we have to offer an open platform for web apps, then we should simply get rid of web apps completely,” Apple thought. The company would rather not allow browser-based applications to anyone in Europe than jeopardize its exclusivity. To comply with the DMA, Apple must ensure that its web-based applications work not only through its own Webkit browser engine, but also through competing technologies such as Chromium.

180 degree bend

Apple is now backing out of these plans, but not out of the goodness of its heart. Ultimately, the EU couldn’t laugh at the strategy. Progressive web applications, PWAs or web apps are applications that look like classic apps, but actually run completely in the browser in the background. They offer developers the opportunity to offer simple apps outside the limitations of the App Store. The EU suspected that Apple was guilty of violating other DMA rules by completely removing this option along with web apps. An investigation was already underway.

“We have been asked to continue to provide support for Homescreen Web Apps in iOS, so we will maintain the existing Homescreen Web App features in the EU,” Apple said. Web apps will be available in iOS 17.4 in March. The European Commission is pleased with Apple’s about-face and says it has already received more than 500 complaints as a result of the previous plan. The interest group Open Web Advocacy has already collected 5,000 signatures for an open letter against the plans.

Support for external engines

It is unclear what further plans Apple has. In fact, the manufacturer now has to bring its web apps into compliance with the DMA, which means iOS has to support other browser engines. The apps must also run on Chromium or Mozilla’s Gecko engine. Apple is reluctant to make this concession, reportedly due to “complex privacy concerns.” Apple does not seem to have any plans to meet these requirements for the time being: exclusivity for WebKit remains intact.