Private client-side-only PWAs are hard, but now Apple made them impossible (andregarzia.com)

Article summary

The article discusses the challenges of creating private client-side-only Progressive Web Apps (PWAs) and how Apple's recent changes to WebKit have made it impossible. Apple's changes erase all local storage data for a given site if the site is not used for seven days, which means that apps must keep data on a server or risk losing it. The author argues that this change hurts the web and forces developers closer to Apple's app store. The author was trying to build a feed reader PWA without a backend server, but Apple's changes have made this impossible.

Main themes

• PWAs vs Native Apps
• Apple's App Store Policies
• Web Privacy and Security
• Developer Challenges
• Walled Gardens
• Cross-Platform Development
• Notarization Rules

What commenters say

• Apple's changes to WebKit are a deliberate attempt to promote their app store and stifle the development of PWAs.
• The changes are necessary for privacy and security reasons, and developers should create native apps if they need more access.
• The restriction on local storage is too severe and will break many web apps that rely on it.
• Users are unlikely to use PWAs if they are not available in the app store, and the installation process is too fiddly for non-technical users.
• Apple's 30% cut of in-app purchases is a major incentive for them to restrict PWAs.
• The web is being subverted by Google and Apple, and developers should be cautious of falling into their walled gardens.
• Native apps are not always the best solution, and web apps can be a better choice for many use cases.
• The notarization rules for native apps on macOS are inconsistent and can change frequently, making it difficult for developers to keep up.