It works like this:
A login procedure is applied when an app gives access to large amounts of personal data that needs to be secured. To be able to log in, the user had to register first.
The log in screen displays two fields, one for username or email address and one for password, along with a dedicated button for logging in. When one of the text fields is tapped…
…the soft keyboard slides into the screen and users can enter their information.
The password is displayed in dots.
The log in button is visible, although only for a part. The user can choose to log in by tapping on the button, or…
he can tap the enter button, making the keyboard slide out of screen. The login button is now fully available to tap on.
By tapping on the login button a progress wheel dialog appears to notify the user their username and password are being authenticated. If the combination is correct, the user is logged in.
Your app handles large amounts of personal data such as name, email address, messages, preferences, billing information, credit card numbers etc. The login can be platform independent, sharing the associated data between pc, web and smartphone.
The login form can provide a link for registering an account in case the user doesn't have one. In addition, it can also display a checkbox for remembering the user, when the user is likely to log out again. Possible and convenient would be to let the user only log in once, and keep him logged in on further visits. This saves the hassle of logging in every time they open the app.
- Log in process is practically always the same, so the user knows what to do
- When the user forgets his password, he has to arrange retrieving it on the app's website