The latest PWA (Progressive Web App) browser scorecards have reignited a fierce community debate about Apple's approach to web app development. While Chrome leads with a score of 97 out of 100, Safari trails at 86, but the numbers tell only part of the story behind a much larger controversy.
PWA Browser Scores (Latest Versions)
| Browser | Version | Score |
|---|---|---|
| Chrome | 131 | 97 |
| Safari | 26 | 86 |
| Firefox | 138 | 82 |
Scores based on support for 14 PWA capability categories including Installation & Core Features, Notifications, Background Capabilities, Device Hardware Access, and System Integration.
The iOS 17.4 Reversal Raises Questions
The most contentious issue centers around Apple's handling of PWAs in iOS 17.4 earlier this year. Apple initially removed PWA functionality in the European Union, claiming that supporting alternative browser engines would create complex security and privacy concerns requiring an entirely new integration architecture. However, after just two weeks of intense backlash from developers and users, Apple reversed this decision completely.
This rapid turnaround has left many questioning the legitimacy of Apple's technical concerns. If the security architecture work was genuinely impractical as claimed, how was it resolved in such a short timeframe? The incident has become a focal point for critics who argue that Apple's PWA limitations are driven more by business interests than technical constraints.
The Decade-Long Notification Delay
Another major point of contention involves push notifications for PWAs. Safari on macOS received push notification support in 2013, while Safari on iOS only gained this capability in 2023 - a full decade later. Both platforms use the same WebKit engine and Apple's own APNs (Apple Push Notification service) infrastructure.
Even after finally implementing push notifications on iOS, Apple restricted them to PWAs installed on the home screen, unlike Android Chrome where they work directly in the browser. This limitation doesn't exist on any other major platform, further fueling suspicions about Apple's motivations.
Key PWA Timeline Events
- 2013: Safari on macOS gains push notification support
- 2023: Safari on iOS finally receives push notification support (10-year gap)
- February 2024: Apple removes PWA support in EU with iOS 17.4
- February 2024: Apple reverses PWA removal after 2 weeks of backlash
- September 2024: Apple threatens to stop shipping products to EU over DMA compliance
Standards vs. Embrace and Extend
The debate has also highlighted tensions around web standards development. Some community members argue that Google is attempting to control web standards by implementing features unilaterally, then pressuring other browsers to follow suit. The BeforeInstallPrompt API serves as a prime example - Google implemented it, but both Mozilla and Apple declined to support it, leading to its eventual removal from specifications.
Web standards are not whatever Google wants. They are arrived at through consensus.
However, critics counter that this standards argument doesn't explain Apple-specific patterns, such as the iOS notification delay or the iOS 17.4 reversal, which involve Apple's own technology on Apple's own platforms.
The App Store Connection
At the heart of this controversy lies Apple's App Store business, which generates over USD 20 billion annually through its 15-30% commission on digital transactions. PWAs could potentially allow developers to bypass this system entirely, creating an obvious conflict of interest.
Apple's recent threats to stop shipping products to the EU entirely rather than comply with the Digital Markets Act have only intensified these concerns. The company has actively fought against regulations that would open up their platform, calling for the DMA to be repealed and explicitly stating that EU users' experience on Apple products will fall further behind.
The Broader Impact on Development
The PWA limitations have real-world consequences for developers and users. Without robust iOS support, PWAs struggle to achieve the cross-platform promise that makes them economically viable. Developers often can't justify PWA investment when they can't effectively reach iPhone users, who represent a significant portion of the mobile market in many regions.
This creates a self-reinforcing cycle where limited iOS PWA capabilities lead to reduced developer adoption, which Apple can then point to as evidence of low user demand. The pattern has frustrated many in the development community who see PWAs as a path toward more open, user-controlled computing.
The PWA scorecard debate ultimately reflects broader questions about platform control, web standards, and the balance between business interests and technological progress. As regulatory pressure mounts and the community continues to push for change, the future of PWAs may depend as much on policy decisions as technical capabilities.
Reference: PWA Browser Scorecards