Product design path: Mobile Application Form Analysis

Imagine a user who has spent a few minutes downloading an application and just opened the preparation attempt, a registration interface appeared in front of him asking for his personal information, so his only choice is to leave. I personally think that entering registration information at the beginning will lead to the loss of potential users. As a developer or product manager, what we should do is first try and then register gradually.

I personally think "left ears" is an example of failure. Although it has a "feeling good" idea and a "Visually tested" user experience, only a few have completed registration. I also downloaded and played games under my colleagues' "publicity", but some inexplicable prompts appeared during the correct registration process. Haha and Nima won't play. I wonder if they noticed it? Write this article several months laterArticleOnce again, the registration page is still annoying!

1. Add users to the application step by step

As the name suggests, step-by-step means to gradually bring users into the app, so that they can truly integrate into the app, so that they can truly appreciate the benefits of the product. What new users need to know most is what the application can do and what services it can provide. Why should I pay attention to this application.

Hiding a password is a common practice when users register and log on to an account, to prevent user passwords from being peeked. Hiding a password is a good security measure, but when a user registers, the situation may seem different. When a user registers an account, they want to easily complete the form. But the hiding of passwords hinders them.

2. Password Hiding is suitable for Logon but not Registration

User logon is more frequent than user registration. The user only needs to register the account once when creating the account, and each time the user accesses their account, logon is required. (currently, many applications do not need to enter the password again after one logon. For details, refer to QQ ,). Because logon is so frequent, you should avoid entering a password in front of other users. Sometimes a user needs to show something to his friends or colleagues on his mobile phone, and he needs to log on to his account to complete the process. Therefore, it is necessary to hide the password in the logon window. This ensures that the password is not peeked into every logon.

However, it is not appropriate to hide the password in the registration window. Hiding a password usually leads to incorrect user input because they cannot see the entered content or know whether the entered information is correct. Input errors during registration are more serious than input errors during logon. If the user enters the wrong password during login, he can re-enter the password. If the user entered the wrong password during registration, the user may be locked during login, or you have to reset the password because you cannot log on for half a day. None of this can blame users. This is the designer's fault. They did not give users a clear picture of the entered password.

What if I ignore the password validation field in the registry list?

The biggest obstacle to hiding a password is the confirmation password field in the registration menu. This field requires the user to enter the password again and match the two passwords to ensure that the entered password is correct. This function is added only when the password is hidden to prevent incorrect user input.

Password validation fields also have advantages and disadvantages. When users have to enter their passwords in two input boxes, they are more prone to errors. Because they cannot see where the error is, they must delete all input in the field and re-enter it. The password validation field will not only cause more input errors, but also force the user to do more work, reducing the user's speed and making registration more painful.

The password is hidden, and the user's incorrect input is hidden, making it difficult for them to discover and correct the password. Most users register in secret and are generally not noticed. Besides, users register only once. So when they are alone, displaying passwords in plain text is not as dangerous as we think. Even if a user registers in a public place, there is a small chance that the password will be peeked.

Another security measure is to show the user's password in small font, light color, and italic. In this case, all characters are visible only when they are close to the screen. After this improvement, even a hacker cannot see the password unless he is sitting in front of the screen.

Show password characters: a mobile phone is a private device. It is very unlikely that users will be peeked at when entering the password. Why not show the password characters? You can also use asterisks to hide password characters. Temporary password exposure can reduce incorrect input and increase the number of user operations, thus improving the user experience to a certain extent.

In short, the purpose of our application is to achieve better human-computer interaction. If a potential user is scared away from the registration interface, will it not give up? The best way to register an application is to do three: first, it is best not to have a registration interface on the app's first screen; second, first experience, then register; 3. Because the registration interface is cumbersome, it is necessary to optimize it.