Progressive web applications (PWAs) for iPhones crashed in the EU, but not as a bug. Apple has updated its website to clarify why PWAs were no longer working in the EU after downloading the latest iOS betas, after developer concerns and news coverage. As expected, the IT giant is blaming the new EU rule, the Digital Markets Act, for the shift, citing the DMA’s complexity in allowing alternative browser engines.
To recap, security researcher Tommy Mysk and Open Web Advocacy found that PWAs were downgraded to page shortcuts in iOS 17.4’s second beta. The original question was whether this was a beta bug (strange things have happened) or a plan to undermine PWAs in the EU, where Apple is being forced to allow alternative app stores, third-party payments, and browser engines. PWAs, which make web applications seem like iOS apps, stopped operating in beta. Developers found that these online applications opened like Home Screen bookmarks.
That meant no “dedicated windowing, notifications, or long-term local storage,” said MacRumors, although iOS 16.4 enabled PWAs to badge their icons with alerts like native applications. When iOS 17.4 beta users accessed a web app, the system asked whether they wanted to open it in Safari or abort. The notice says the web app will “open in your default browser from now on.” Since Safari webpage shortcuts don’t save data locally, users reported data loss. Notifications stopped working.
There was cause to doubt that the modification was purposeful. Apple did not respond to Eltry’s persistent requests for comment. (We asked Apple to clarify whether this was a beta issue or an intended adjustment and explain why.) The Verge reported that Apple “appears to be” breaking PWAs in the EU after the next beta version, without an official statement from Apple.
Apple answered in its own way. To resolve the issue, it updated its website with EU DMA modifications today. In a recent post, the business claimed that it had to make so many modifications to iOS to comply with EU requirements that PWA support was out.
Apple said iOS traditionally supported Home Screen web applications by building directly on WebKit and its security architecture. That enabled web applications to match native app security and privacy. Apple must enable other browser engines under the DMA. It claims that without the isolation and enforcement of WebKit-based web app restrictions, rogue applications might be installed that read data from other web apps or “gain access to a user’s camera, microphone, or location without a user’s consent,” Apple stated.
The DMA’s other demands and Home Screen web apps’ low user adoption made it impractical to build a new integration architecture to address the complex security and privacy concerns of web apps using alternative browser engines. To meet DMA standards, we removed the Home Screen web application functionality in the EU, the website says.
The company confirms developers’ worries that PWAs were essentially blocked in the EU by allowing EU users to bookmark webpages on their home screens.
We anticipate that this change will have a small impact on users. We regret any effect this move, designed to comply with the DMA, may have on Home Screen web app developers and our users, says Apple.
Critics say Apple will cripple web app capabilities for its consumers to maintain its influence in the iOS app market. Apple’s supporters will likely say the company’s explanation is acceptable and supports iOS safety. As always, the truth is likely in the center.
Apple has not replied to inquiries.
Apple says it intentionally breaks EU iPhone web applications.
