Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While I too wish for better support for PWAs in iOS, the way push notifications are implemented in PWAs and iOS are fundamentally incompatible. iOS requires all push notifications to go through Apple's push server, which means there is only one long-poll connection to check and significant battery savings. Whereas, Google's PWA docs[1] literally lists random-push-service.com as the push server.

[1]: https://developers.google.com/web/fundamentals/push-notifica...



Safari on macOS already implements a proprietary web push technology using APNS. Push providers like OneSignal already support it.

It is 100% compatible with the way notifications work on iOS.


A long poll connection (i.e., a TCP connection not sending packets) uses exactly 0 joules of battery until something is sent.


That's not true. Long pools cannot have an indefinite timeout, especially for a mobile use case. Plus, it's not just the TCP connections. If you look at push notifications on Android phones in China, because GMS isn't available, every other app is having a background thread checking for push notifications. It adds up.


From that page:

> Each browser can use any push service they want, it's something developers have no control over.

The browser dictates the push service to use, not the developer of the web app. That URL is for the app developer to push content to.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: