On iOS all notifications have to use Apple's Push service.
And the WiFi essentially has to allow the Apple push notification system entirely in order for iMessage to work fully the way people expect.
So it's really a side effect. But yeah for example with the free iMessage connection on Southwest, I can see all the notifications come in on Discord, but of course I cannot connect within the discord app to actually load all those messages. I can only read them as they come in as push notifications.
>On iOS all notifications have to use Apple's Push service.
Have to?
Isn't there an option to send 'offline' notification? I mean, coming from the app itself, rather then external callback? With that, app could ommit the official way of using Apple Push service, no?
Well, apps can only "run in the background" for up to 10 minutes.
So sure, an app can generate a notification popup itself, but it's pretty limited as it won't be able to generate a notification after being backgrounded for more than 10 minutes.
And the 10 minutes is also only if the app is designed to extend the duration as long as possible. Normally it would get cut off after 1 minute.
So because of this it seems that in the vast, vast majority of cases apps choose to send their notifications from the Apple Push notification service.
Yea but those mean the app has to be running. The main advantage of Apple's Push is that the app can be put to sleep and only wake up when you tap a notification.
And the WiFi essentially has to allow the Apple push notification system entirely in order for iMessage to work fully the way people expect.
So it's really a side effect. But yeah for example with the free iMessage connection on Southwest, I can see all the notifications come in on Discord, but of course I cannot connect within the discord app to actually load all those messages. I can only read them as they come in as push notifications.