How to design an App login module

I have previously explained and discussed with you many articles and viewpoints on the design of mobile APP login interface.

Today, let’s talk about APP login design methods and how to design these interesting APP login modules from the perspective of mobile APP product managers.

If you are a mobile APP product manager, the following useful information is worth your collection!

The purpose of designing APP login that the editor is discussing with you is mainly to consider the security and convenience of user information.

1. Be familiar with the common mobile APP login methods

① Account login (mobile phone, email)

② Third-party login (WeChat, QQ, Weibo)

③ One-click quick login (tools, such as memorizing words)

④ Visitor login (bbs)

⑤ Demo test login (such as Umeng, etc.)

⑥ Gesture login, voice login, fingerprint, face recognition

Such as WeChat voice login, iPhone fingerprint unlocking and so on.

Basically, there are as many ways to register as there are ways to log in. The logic of each method is slightly different.

Currently, the most popular login methods on the market are account login + third-party login. Here are the points that need to be considered using these two common login methods as examples.

2. Understand the login logic of the APP login module

Basically, most app login interface designs are as follows:

The main interface is divided into: important information area + operation area

General login logic analysis:

• Login macro process (several steps, several pages, considering the number of user operations, interface display)

• Tips for user misoperations during the process (restrictions generally involve input rule errors, input times exceeding the limit, and input authenticity errors)

• The landing page for login jump (when to let users log in)

• Forgot password process (WeChat’s solution is good)

3. Business logic of the login module that mobile product managers must consider

"It is rogue to talk about functional logic without considering the product."

That is to say, the key to registration and login logic depends on the product form.

Talking about functional logic must follow business logic. In your business, what are the benefits of registration and login respectively, and why users need to register and log in? If these logics are not sorted out, it is worthless to talk about general content.

[[151756]]

If you want to spread the word of a product in large numbers, whether it is a web or an app, the most effective way may be to use third-party authorized login for social products, and then provide registration guidance after login, or not, because your business logic requires users to spread the word in large numbers, rather than leaving specific information about users.

If it is a transaction product, whether it is a Web or App, the priority is security issues, so when registering, users should fill in as much real information as possible and complete relevant verifications, and the password security level should also be high; login security should also be considered, and login controls are probably inevitable.

If it is a tool-type product, then registration should be simple enough, and logging in or not should not be an option that prevents users from using the product.

And so on, business logic analysis of the hypothetical APP login module.

[[151757]]

***Share the following 8 suggestions on login and registration modules with all mobile APP product managers

• Do I need to log in when I open the app?

• Or do you only need to log in when you need to fill in delivery information or leave a comment?

• The most convenient way to log in is to use QQ, WeChat, or Weibo for joint login. However, after joint login, you must not ask users to enter their mobile phone number or other registration information.

• If the user must re-register, or to verify the valid identity, it is recommended to use the mobile phone number, which reflects the timeliness of the information push;

• When entering a password, ask the user to enter it once, and then use plain text;

• Considering the security of passwords, it is recommended to post-set them, that is, to give users the easiest setting process. For example, you can allow users to set a 6-digit login password. How to ensure the security of user accounts? Set rules based on the number of logins, locations, and operations. Don't make it difficult for users when registering. Thank you;

• Verification codes and the like must only be entered by users when they register multiple times with the same device, or when they "swipe (log in to multiple accounts with one device)". Under normal circumstances, users must be given the most relaxed experience. Password security and verification codes are tricks used when encountering abnormal users. Abnormal users must have characteristics, and tricks are used based on the characteristics. Otherwise, it is very easy to kill a large number of ordinary users.

• After registering/logging in, you must directly switch back to the process node that requires login. After registering/logging in, you must directly switch back to the interface that requires login.

I would like to share the above information with you all. At the same time, I also hope that you can use your creativity in the APP login module and share your excellent works with us.