I'm just working on this now in Wire Android's app. Notifications are a huge pain in the bum even in the best network conditions. So many edge cases... But yes, we cache them.
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.
-
-
-
Good work! So many apps don't, and if my network is down, not only do I miss the thing I wanted to see, but I lose my only link to it when the notification goes away... though I suppose that's a different API misusage.
End of conversation
New conversation -
-
-
Maybe they're testing using office wifi. ;-) But assuming perfect conditions can often be seen in testing in general.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This along the same lines as "I prefer no wifi to slow wifi"
-
I'm tempted to refine this further! I care less about the speed of the wifi than the consistency of its speed.
End of conversation
New conversation -
-
-
The first rule of mobile app development - assume that there's no network. I learned that with the Palm VII back in 1999. :-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
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.
-
We can tell OS how to handle notifications when the app is in background. In Android it's done via FCM (https://stackoverflow.com/questions/37711082/how-to-handle-notification-when-app-in-background-in-firebase …). But it's not reliable. It's safer to treat it only as a nudge: "hey, there's something for you!" and then ask the server directly for notifications.
- Show replies
New conversation -
-
-
And please put in proper network timeouts, losing connection whilst opening an offline enabled app should not freeze it for 30+ seconds.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.