If you can’t express it, you don’t know it well enough.
— Albert Einstein
Since I am in charge of the account system recently, I will list the problems that product people are prone to in the daily demand. Share yesterday, since the account system in the early product layer is more in the login and registration of the landing your data is the same person or two accounts? Account system CASE, login exception and logic is much simpler than registration.
Here for the registration of the third party registration to make an easy point of error, add a point is that the following two schemes will enter the verification code after the page for verification. In order to focus on error-prone points, I have left the same page unshown
Solution 1: Enter the third-party registration password
In such a product design, we still let users continue to fill in their accounts and passwords after third-party registration.
The reason for this is that if no password is set for the registered users, the subsequent users can only log in through wechat, and there is no password in the user’s product account. The product wants users to use more accounts and passwords to log in to cultivate users
Scheme 2. You do not need to enter a password for third-party registration
In such a scenario, it seems very simple for users to register with a third party. You only need to log in to a third party and enter the mobile phone number and verification code. Unless the user later sets a password in the personal center, they can only use wechat login to use the product.
The reason for this product design is that since users have chosen a third party to register, they certainly do not want to set a password. To quickly experience whether your service meets expectations or not, if the product or service keeps the user, the user will use the password to log in conveniently later.
Two options. Plan one or plan two?
In both account systems, registration schemes have their own benefits. However, one is biased towards the product and hopes to educate users. The other is to let users choose a good way to form a habit. The reason why I throw this question to you is that I personally think both schemes have reasonable aspects.
Different products and scenarios require different account systems. As mentioned above, momo’s account system must be young, fun and cool, while Meituan or Dianping’s account system must be simple, fast and does not require outstanding interaction effects.
Personally, if your product has become tens of millions of users, then you can iterate your registration logic and let users get used to your way of registration. If your product is just getting started or going from 0 to 1, adapting to trends and seeing how most similar products or Internet products are built will reduce errors.
What’s your answer? Let’s talk in the comments
I will insist on 2 original articles every week, today’s share is here, be there or be square ~
In addition, my first book “From Zero to One: PM changes the World” was officially launched as an electronic file. This book summarizes 222 original products, covering the content of product manager interview, algorithm, interaction and other different dimensions. If you are interested, you can reward and leave a message on your email. I will send an email to you around 12:00 noon every day (hope you do not spread support, support copyright). If you need to preview the book outline, jump to the link
A book for yourself and product people: from zero to one.
If you can’t express it, you don’t know it well enough.
— Albert Einstein
Since I am in charge of the account system recently, I will list the problems that product people are prone to in the daily demand. Share yesterday, since the account system in the early product layer is more in the login and registration of the landing your data is the same person or two accounts? Account system CASE, login exception and logic is much simpler than registration.
Here for the registration of the third party registration to make an easy point of error, add a point is that the following two schemes will enter the verification code after the page for verification. In order to focus on error-prone points, I have left the same page unshown
Solution 1: Enter the third-party registration password
In such a product design, we still let users continue to fill in their accounts and passwords after third-party registration.
The reason for this is that if no password is set for the registered users, the subsequent users can only log in through wechat, and there is no password in the user’s product account. The product wants users to use more accounts and passwords to log in to cultivate users
Scheme 2. You do not need to enter a password for third-party registration
In such a scenario, it seems very simple for users to register with a third party. You only need to log in to a third party and enter the mobile phone number and verification code. Unless the user later sets a password in the personal center, they can only use wechat login to use the product.
The reason for this product design is that since users have chosen a third party to register, they certainly do not want to set a password. To quickly experience whether your service meets expectations or not, if the product or service keeps the user, the user will use the password to log in conveniently later.
Two options. Plan one or plan two?
In both account systems, registration schemes have their own benefits. However, one is biased towards the product and hopes to educate users. The other is to let users choose a good way to form a habit. The reason why I throw this question to you is that I personally think both schemes have reasonable aspects.
Different products and scenarios require different account systems. As mentioned above, momo’s account system must be young, fun and cool, while Meituan or Dianping’s account system must be simple, fast and does not require outstanding interaction effects.
Personally, if your product has become tens of millions of users, then you can iterate your registration logic and let users get used to your way of registration. If your product is just getting started or going from 0 to 1, adapting to trends and seeing how most similar products or Internet products are built will reduce errors.
What’s your answer? Let’s talk in the comments
I will insist on 2 original articles every week, today’s share is here, be there or be square ~
In addition, my first book “From Zero to One: PM changes the World” was officially launched as an electronic file. This book summarizes 222 original products, covering the content of product manager interview, algorithm, interaction and other different dimensions. If you are interested, you can reward and leave a message on your email. I will send an email to you around 12:00 noon every day (hope you do not spread support, support copyright). If you need to preview the book outline, jump to the link
A book for yourself and product people: from zero to one.