PWAs wont replace native iOS apps

Original Article ↗ Hacker News Discussion ↗

Progressive Web Apps (PWAs) are running into hard limits on iOS, with Apple restricting capabilities such as full-screen installable web apps, persistent local storage, and push notifications—especially for EU users under its response to the Digital Markets Act. Commenters argue over whether these gaps are inherent to web technology or the result of deliberate platform lock‑in to protect App Store revenue, contrasting Apple’s approach with more PWA‑friendly support on Android and desktop. Many see PWAs as a cheaper, cross‑platform way to ship apps that might not exist otherwise, but concede that on iOS they are currently a second‑class option unlikely to replace fully native apps in the near term.

Apple’s treatment of PWAs on iOS

  • Many argue Apple is deliberately hobbling PWAs to protect App Store revenue and gatekeeping power (no silent push, broken dark mode, long‑standing bugs, missing APIs).
  • Others note Apple has added substantial PWA features over the last ~4 years, claiming this undercuts the “Apple wants PWAs to fail” narrative.
  • Several see Apple’s behavior as classic “malicious compliance”: doing the bare minimum, then rolling features back when regulation forces real openness.

EU / DMA and iOS 17.4 changes

  • In the EU, “Add to Home Screen” PWAs are turned into simple browser bookmarks:
    • No standalone window, no persistent local storage continuity, and no PWA push/badges.
    • Some report data loss and broken notifications after this change.
  • Apple’s justification: integrating Safari PWAs with the Home Screen would “favor Safari” over alternative engines, violating the DMA.
  • Critics say Apple could have instead opened the same integration to other engines, and view the removal as retaliation and user‑hostile.
  • Unclear: whether DMA legally required removal vs Apple choosing the most self‑serving interpretation.

Technical limitations & UX issues on iOS

  • Current PWA limitations on iOS mentioned:
    • No true silent push for badge sync; workarounds like delayed notifications are clumsy.
    • Broken or inconsistent dark mode behavior for months.
    • Installation flow via “Add to Home Screen” is unintuitive compared to app‑store installs.
  • In the EU builds, PWAs lose full‑screen app-like chrome and local storage continuity, further degrading UX.

Android and other platforms

  • Android PWA support is described as “much better”:
    • Native install prompts, beforeinstallprompt events, per‑engine PWAs (Chrome, Firefox), and more reliable behavior (e.g., light/dark mode).
  • Desktop experiences (especially with Edge) are cited as very good; PWAs can feel “98% native”.

PWAs vs native apps (trade‑offs)

  • Pro‑PWA views:
    • Cross‑platform, one codebase; avoids App Store fees, reviews, and hardware requirements.
    • Enables small, internal, or hobby apps to exist at all, especially for iOS without a paid dev account.
    • Instant updates; no 100MB app‑store downloads.
  • Pro‑native views:
    • Better integration, smoother UI/animations, richer APIs, and fewer browser quirks.
    • Cross‑platform/web stacks are seen as “cheaper but worse”; serious, polished apps should be native.
  • Some predict a hybrid future: PWAs plus thin native shells (Tauri/Capacitor‑style) via alternative app stores, if iOS rules loosen.

Strategic responses

  • Suggestions include publicly warning users that missing features are due to iOS/Safari limits, and encouraging “for best experience, use other OS/browser” messaging.
  • Others argue boycotting iOS is unrealistic because that’s where much of the paying user base is.