When I open my Android Emby app, two scenarios are possible:
- Connect Successfully
- Connection unsuccessful. Go to server configuration.
Well... it happens that JUST because my server wasn't reached, it doesn't mean there's something wrong and I have to be redirected to config pages. Sometimes it's just about waiting a few seconds and trying again (or even insisting a little more before giving up connection).
I believe that this breaks Emby's connection transparency. I think that the best way would be to create a sidepanel that, WHEN DESIRED, could be slided in to reconfigure, connect manually or even emby connect. This way... Emby would retry non-stop (maybe with a tries counter, "retrying in N sec..."), until you REALLY want to manually configure it again.
I'm thinking about installing Android Emby app on my wife's phone, but she is far from a tech user, and those users will cleary be confused with config pages. Common users hate config screens and just want app to work... even if takes a little while to connect.
What do you think?