Apple confirms iOS 17.4 removes Home Screen web apps in the EU

Original Article ↗ Hacker News Discussion ↗

Apple’s decision to remove Home Screen web apps (progressive web apps, or PWAs) for EU users in iOS 17.4, citing Digital Markets Act compliance and security concerns, is seen by many as a major setback for open web technologies. Commenters debate whether PWAs were ever widely used or viable, with some arguing they were already “dead” and others saying poor platform support—especially from Apple—kept them from reaching their potential. The move is also framed as “malicious compliance” that protects Apple’s App Store business model, highlighting broader tensions between regulatory goals, user choice, platform security, and gatekeeper power.

Impact on PWAs and the Web

  • Many see this as effectively killing PWAs on iOS in the EU and seriously damaging the future of PWAs as a cross‑platform app model.
  • Others argue PWAs were already niche and little-used, so most users won’t notice; some even welcome fewer web‑tech apps.
  • Loss isn’t just for “full” PWAs: simple home-screen shortcuts to responsive webapps also become less convenient.

Apple’s Rationale vs Suspected Motives

  • Apple’s stated reason: supporting home-screen web apps with third‑party engines under the DMA would require a new integration architecture, not worth the effort given low usage.
  • Many commenters call this “malicious compliance” or “spite,” arguing the DMA doesn’t require PWAs to be removed and that Apple benefits by pushing developers toward native apps and App Store fees / CTF.

Security and Privacy Debates

  • Apple cites complex security/privacy concerns (sandboxing, per‑site permissions, JIT attack surface) if multiple engines gain deep system integration.
  • Critics respond that:
    • macOS, Android, Windows already allow multiple engines and PWAs;
    • native apps are at least as risky;
    • removing a niche feature doesn’t meaningfully improve security.
  • Some technical discussion suggests current iOS PWAs may share a WebKit instance that enforces per‑site prompts; moving to multiple engines would require a major redesign.

Regulation, DMA, and Unintended Consequences

  • One camp says this is exactly the kind of side-effect you get from regulation; people should “own” that outcome.
  • Others insist the DMA doesn’t force PWA removal and expect further EU pushback or stricter future rules in response to Apple’s approach.

User Adoption and Perception of PWAs

  • Several note almost no mainstream awareness of PWAs; interest is mostly among developers and “nerds.”
  • Some argue poor platform support (especially from Apple, and even Firefox desktop) is why PWAs never took off, not lack of intrinsic value.

Developer and Ecosystem Concerns

  • Small and indie developers are seen as big losers: now effectively pushed toward costlier native development and store policies.
  • Some developers say this, plus other recent Apple moves, makes them rethink targeting Apple platforms or new ones like Vision Pro.
  • A subset of users and devs say this pushes them toward Android or more open platforms in the long run.