Comment by Gareth321

> Is Chrome's PWA support on Android a massive glow to Android Play Store's bottom line?

Probably, but Android allows side-loading. iOS does not.

> What's iOS missing for PWA's to be a viable money-maker for companies?

Brace yourself.

1. Notifications are hobbled. This is HUGE. Silent pushes, rich notifications, NSE, reliable badge counts, and reliable delivery. This is made worse by:

2. Hobbled background priority. PWAs are aggressively suspended and killed. No long running processes. No guarantee of process execution. IndexedDB and in-memory state may be wiped at any time.

3. PWAs can’t access most system frameworks. Bluetooth (CoreBluetooth). NFC (Core NFC). Background location tracking. HealthKit. HomeKit. CallKit / VoIP. Siri Shortcuts / App Intents. AirDrop. Apple Pay (full API). CarPlay. System share extensions.

4. No access to native rendering pipelines. Performance is severely limited.

5. PWAs have unstable, purgeable memory. No persistent file storage.

6. Limited UX and lifecycle control. No termination callbacks. No suspend notifications. Reloaded arbitrarily. Back/forward gestures conflict with browser.

7. No access to native UI components like FaceID, native text fields, drag and drop across apps, context menus, and haptic feedback.

Apple has done everything they possibly can to ensure PWAs are broken on iOS.