The common login box design elements on the Internet mainly include seven points, namely : account password input box, authentication capability, service agreement, registration process, password finding process, user FAQ, and user feedback system .
account password input box
The user enters the account password to log in to the text box of the application.
Design Points:
User information security protection. Identify non-natural persons logging into the application. Reminder after the user enters the wrong password limit, and the process reminder of the forgotten password.
Design suggestions:
The focus is on the security of the user's personal account information and the anti-swiping mechanism for account encryption.
Authentication ability
That is, the ability of the product to authenticate the user's real identity. At present, common methods include SMS verification code authentication, password-free login, email authentication, and third-party login.
Design Points:
Focus on the characteristics of the capabilities themselves, and choose the capabilities that suit your products. When product managers introduce certification capabilities, they need to consider clearly the product usage scenarios, processes, product technical capabilities, and costs. For example, the cost of SMS verification code is high, and the cost of password-free login is low, but the access needs to pass the operator's review mechanism.
Design suggestions:
In addition to focusing on what your product needs, the choice of capabilities should also pay attention to the characteristics of the capabilities themselves, so as not to introduce capabilities that do not meet the standards and "retain pitfalls" for subsequent product use.
service agreement
The service agreement reached between the product and the user usually appears on the homepage or registration page of the login box. If it involves a scene that requires the user to know or confirm multiple times, the service agreement will automatically pop up, and the user is forced to read and confirm from the design.
Design Points:
The service agreement is just needed, and it stipulates the agreement reached by the user using the product. Some products will omit the service agreement intentionally or unintentionally. In fact, the service agreement is very important for the application, because the service agreement is like the agreement between the product and the user Book, in necessary scenarios, can protect the security of product applications and avoid unnecessary losses.
Design suggestion: Don't ignore the service agreement, the content of the agreement should be as detailed as possible to avoid unnecessary legal disputes.
registration process
When the user uses the app for the first time and does not have the product login permission, the registration process needs to be used, or, when the app cannot identify whether the user is a product user, the product will automatically pop up the registration process for the user.
Design Points:
The registration process needs to be as simple as possible to avoid the loss of new users. After the user registers, the system can accurately record the user's registration information, account password, etc.
Design suggestions:
Registered design, with simplicity as beauty.
Find secret process
When the product uses the account password login process, if the user forgets the product login password, it is necessary to design a password recovery process to allow the user to retrieve the personal account secret.
Design Points:
The password finding process is the process of re-authenticating the user's identity, and the key point is to authenticate the identity.
Design suggestions:
The focus of the password finding process is authentication. It is not recommended to design the password finding process to be too long or increase the operating cost to avoid the loss of users in the password finding process.
User FAQ
Answers to common questions in the user login authentication process, etc., can be designed according to the usage scenarios and planning of the product, and are not an essential element in the design of the product login box.
Design suggestions:
The presented FAQ should be a summary of frequently asked questions by users, and the answers to the questions should be easy to understand and easy to understand. Count the number of times each question is opened, so as to count which questions are frequently encountered by users, and provide reference for subsequent product design and optimization. User Feedback System
Users can give suggestions or feedback on problems during product login or use, which are generally designed on the product login authentication process interface or personal information display page, not an essential element in the product login box design.
Design suggestions:
The user feedback system requires the collection and sorting of user problems and needs to be used in conjunction with the product platform. It requires the product manager to pay attention to the interaction between the front and back of the product and the transmission of feedback data when designing. After users give feedback, they generally hope that the product will give a response or answer. It is recommended that professional customer service personnel follow up on user feedback and suggestions. Summarize
The design of the login box seems plain, but it contains delicacy and wisdom. The details reflect the product manager's design skills and grasp of the product user group. The login box design has three standards and seven elements. I hope it can attract more ideas and dig out more Login Box Good Design Composition and Thought.