Currently, when zmNinja launches, the default is to try and authenticate with the previously used server. The issue is that some servers may not be accessible from outside of their native LAN (i.e. launching the app using cellular data as opposed to WiFi) or perhaps the user wants to log into a completely different server than before. This, in turn, causes a 10-15 second delay before the authentication times out and only then the user is able to then select which server they want to choose.
Propose that upon application launch, the user is greeted with a menu of server to choose with the last one highlighted. The user can then choose the proper server by either simply tapping on the name, or perhaps tapping followed by pressing on 'Login' button to proceed.
Currently, when zmNinja launches, the default is to try and authenticate with the previously used server. The issue is that some servers may not be accessible from outside of their native LAN (i.e. launching the app using cellular data as opposed to WiFi) or perhaps the user wants to log into a completely different server than before. This, in turn, causes a 10-15 second delay before the authentication times out and only then the user is able to then select which server they want to choose.
Propose that upon application launch, the user is greeted with a menu of server to choose with the last one highlighted. The user can then choose the proper server by either simply tapping on the name, or perhaps tapping followed by pressing on 'Login' button to proceed.