Shulou(Shulou.com)06/03 Report--

First, the factors to be considered in the registration module

The following factors need to be considered in    registration module:

Account registration password registration verification code registration button registration account generally have: mobile phone number registration mailbox registration mobile phone number + user name registration password is usually considered as follows: enter the password only once Or whether to enter the password twice requires the user to manually select whether the password is visible. The main points to consider are as follows: whether to use the digital CAPTCHA or the graphic CAPTCHA within a period of time, whether there is a limit on the number of times entered by the registration button. The general design idea of the registration button is as follows: whether the registration button can be clicked at the beginning and when the registration button is clicked is the best opportunity after clicking the registration button. How to effectively prompt the reason why the user failed to register without affecting the beauty of the interface and not making the user feel irritated? finally, the user can effectively locate the place where the input failed and whether to log in directly after successful registration. 2. The business logic of the registration module registers with the mobile phone number.

When    registers with a mobile phone number, it is generally considered to obtain the verification code through SMS, which can effectively prevent users from entering the wrong mobile phone number. However, if the user clicks to obtain the CAPTCHA many times, excluding the intentional CAPTCHA, what the product developer is asked to consider is whether the user cannot receive the CAPTCHA because of entering the wrong mobile phone number or other reasons, so, when the user clicks to get the CAPTCHA for the second or third time, an interface pops up that allows the user to verify that the CAPTCHA is not available for which reason. The common reasons are as follows:

Is the mobile phone number entered correctly? Does the phone have a signal? Is the phone turned off? Is the mobile phone unable to get short messages due to arrears?

Register using mailbox

If    uses an email address to register on the mobile, it is generally recommended to prompt the user whether to use this email address to register after verifying the correct format of the email address. This is mainly because it is not recommended to confirm the email address when registering with the email address on the mobile end (for example, logging in to the email address is very tedious and difficult to compare with the PC side). Therefore, once the user enters the email address but does not confirm it, it is possible that the user entered the error and did not find it. Therefore, it is common to prompt the user to confirm whether the registered email address is to be used when verifying that the registered email address is properly formatted and available.

Register with user name

   generally uses only user names to register products that may not have an email address or have a mobile phone but no mobile phone number, or to reduce typing. Because there is no other means of authentication, in order to prevent the user from typing errors, the user is usually prompted to confirm whether the user name should be used when verifying that the registered user name is in the correct format and can be used.

Register with mobile number + user name / register with email address + user name / register with mobile number + email address / register with mobile number + email address + user name

Generally speaking,    can only consider one of these modes when users must log in with a unique user name, or if they want to provide multiple login methods for users to choose and verify at the same time. These modes combine the registration processes of separate modes. In general, if it is not necessary, you can ignore these three modes, but prompt the user to supplement the remaining two modes in the user's personal information setting interface after the user normally registers with one mode and logs in successfully. In this way, users can directly use any of the three registered accounts as login accounts and have the same password.

Third, how can some thoughts about the registration module effectively simplify the registration process?

   if a registration process contains only three entries: registration account, password and CAPTCHA, the simplified process can actually start with reducing the "invalid input" of users, such as:

At the beginning of the registration interface, all you need is an input box to enter the registration account, and a button to check whether the account is correct (such as the button to get the CAPTCHA, which is part of the registration process. At the same time, you can also directly check the registration account). If the account exists, it prompts the user whether to log in directly with the account; if it does not exist and the account format is correct, other input boxes are displayed. There are two reasons for this:

(1) from the user's point of view, a considerable number of customers like to obtain the verification code after all the contents have been typed, and then find that the account already exists and can log in directly with this account, which wastes the time of entering the password.

(2) from the point of view of app design, some app like to put the operation of obtaining CAPTCHA at the end of the whole input process, subconsciously letting the user obtain CAPTCHA finally.

In view of this,    usually considers the following design solutions when designing a registration module to enhance the user experience:

Place the button to get the CAPTCHA as close to the registered account as possible, if possible, after the user enters the account, check whether the account exists (this is the main purpose) or whether the account format is correct. For example, Didi, whether it is registering or logging in, only allows the user to enter the mobile phone number, and then the "next step" gives the verification code, if the account exists, log in directly, if it does not exist, register and log in. Actually consider what kind of account form to register, not all products need mailbox / user name. Please be sure to remind the user amicably whether the current network status is OK after the registration interface is loaded successfully. If not ok, don't wait for the user to enter everything correctly, happily ready to enjoy the happiness that the product brings to TA, it gives him a bolt from the blue-your network is not in the service area! Usually in order to prevent malicious acquisition of digital CAPTCHA and increase the cost of the enterprise, when using mobile phone number to obtain CAPTCHA, there is a time interval between two operations to obtain CAPTCHA, or there is a limit on the number of times to obtain CAPTCHA within a period of time. You can set the time interval (in general, 60 seconds / 45 seconds / 30 seconds) and the number of operations (such as 3 / 5 / hour, 5 / 8 / day, etc.) according to your actual situation. For graphic CAPTCHA, it is recommended that you do not make this setting, which is basically meaningless. How to effectively prompt the user to enter what format of content? Take the app of iOS, for example, if you just write the format in the placeholder of UITextField, you may not be able to display all the prompts because of the broadband problem in textField. In order to enable the user to enter content in the correct format for the first time, consider that every time the user clicks an input box to prepare the input, a small interface pops up to list the key points of the format required by the input box one by one. Which point has been completed, it will show the completed status. If designed in this way, please be careful not to let the pop-up small interface block the next input box, so consider placing this small interface above or to the right of the current input box. How to consider the encryption scheme when registering (password is encrypted by MD5 and then uploaded; upload using POST mode, etc.)? How is the input information at registration verified (server-side or client-side authentication?) ? Do you need to convert the registration information to json format and then upload it to the server? After successful registration and login, do you need to save the relevant information locally? In the registration interface, how can you clearly prompt the user to "log in"? If the user accidentally closes the registration interface when registering, and usually destroys the registration interface during the design process, do you need to consider if the user accidentally closes the registration interface when the registration is not completed? save the information that the user has filled in locally, and when the user enters the registration again, call the completed content to allow the user to continue to register? If the user registers and logs in successfully, the saved semi-registration information can be emptied directly.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.