When picking up the remote while in standby (disconnected from WiFi) the current behavior is not very intuitive. All you get is a tiny "no wifi" icon in the top status bar. When pressing a button in this state an error message pops up.
A better behavior would be the following:
Show a large "reconnecting" spinner on the screen which prevents touch screen actions. This screen should be dismissable though, in case the user needs to enter the remote settings for example.
Physical button presses in this state should be queued. If queuing all button presses is not feasable, at least the last button action should be remembered and executed, as soon as the remote is connected to WiFi.
Especially the button queuing is quite important. Without it the remote is basically unusable without the "prevent standby in this activity option".
Additional context
Usage scenario:
Watch a movie through an activity, which allows the remote to go to standby
Let the remote enter standby mode (disconnects WiFi)
Press the pause button while the remote is asleep because the doorbell is ringing (for example)
In this scenario you cannot wait until the remote is reconnected to WiFi again. You simply press the pause button and this has to work.
Is there an existing issue for this?
Description
When picking up the remote while in standby (disconnected from WiFi) the current behavior is not very intuitive. All you get is a tiny "no wifi" icon in the top status bar. When pressing a button in this state an error message pops up.
A better behavior would be the following:
Especially the button queuing is quite important. Without it the remote is basically unusable without the "prevent standby in this activity option".
Additional context
Usage scenario:
In this scenario you cannot wait until the remote is reconnected to WiFi again. You simply press the pause button and this has to work.