Smartphone notifications when you don't have a good network connection are hugely frustrating. Apps should be required to cache anything they choose to display a notification about before they show it. Unfortunately, I think most testing assumes perfect network connectivity.
-
Doesn't work like that, though. Unless app is in the foreground, notifications are delivered to, and displayed by, the OS. First the app gets to hear about it is if the user taps on it.
But how does the OS know what things there are to notify the user about? Surely that comes from the app...? I'm saying that the caching should be done at the point the notification message is created, (and retained maybe for a few days).
-
-
In most cases it actually doesn't come from the app, it comes from a back end server. Server sends a message to Google/Apple, and G/A deliver it to the phone. The app plays no part until notification is tapped.
-
This Tweet is unavailable.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.