3 ms·
> Wouldn’t it be great if the user could just pick a “push notifications provider” in the phone settings and OS managed all these hard details by itself? So eve
by xg15 8y ago
> Wouldn’t it be great if the user could just pick a “push notifications provider” in the phone settings and OS managed all these hard details by itself? So every app, which doesn’t want to be policed by the platform owner, didn’t have to invent the system anew? It could be end-to-end encrypted between the app and the app server. There’s no real technical difficulty in that, but as long as our systems are controlled by big players who do not allow this, we have to solve it by ourselves.
Fking this. ideally, this would also involve a standard API on the backend for how to send push notifications. E.g., something like:
1) App on phone queries OS for selected push provider.
2) Phone OS returns some metadata about the push provider to the app, including a a backend URL for sending messages.
3) App sends that URL to it's own backend server.
4) When a push message should be sent, the app's backend server invokes that URL with the message to be sent in some standardized way.
If - which is likely - push servies require that developers register their apps with them before use, this could be expanded by the phone OS returning a list of providers instead of just one.
- metildaa 8y agoI would encourage app developers to take a look at the network architecture of the major US carriers while determining how to give their app notifications from the server. In the US, the 4 major LTE cellular carriers operate IPv6 only networks with NATed IPv4 access tunneled in as an unsupported afterthought. From my testing with IPv6 enabled VOIP for inbound calls, compared to FCM with calls coming from an IPv4 only server, only the former setup would reliably get calls to a test device on the first ring. If you need very low latency push notifications, IPv6 and FCM/Apple Push Notification are needed for best performance. Thus far, inter-carrier roaming generally does not support IPv6, so you still must support legacy IPv4 to a degree.
- StudentStuff 8y agoTo this end, Apple has been leaning on developers to support iOS devices that are on IPv6 only networks: https://developer.apple.com/support/ipv6/ https://developer.apple.com/support/ipv6/