More simple user account design: Just need my actual name, e-mail and mobile phone number choice one, no password

Recently see Dropbox user Registration feature design, simple is simple, but also need to enter a password, set the password means the user's memory burden.

And then thought of the rubbish of the website, although can use other sites of the account landing, but actually still want to enter a lot of privacy information to register, to do.

So I remembered and free WiFi: What data does a really simple user account design need? Only need my actual name, e-mail and mobile phone number optional one, no password!

When need to bind the login device to the mobile phone, automatically through the app to provide mobile phone number, and then send a verification of the site digital text messages, users use it to log on. In order to avoid duplicate validation, the session will be valid for a period of 1 months. Of course, there are some additional suspicious login recognition techniques based on machine learning.

e-mail and mobile phone number optional one means that should not be provided at the same time, e-mail and mobile phone number can register 2 accounts, which is actually no problem,

Need my actual name means that the user name and (e-mail address OR mobile phone number) federated as the user database of the natural primary key, the user name itself allows duplication. In fact, the biggest problem with a custom ID number being the primary key is that once someone has a good ID, the person behind it will have to do the staring. This one's too much.

The better design is that once the user has completed the registration, he can freely define an ID as his nickname.

There is also a benefit of using the user's actual name, which is the potential to allow social interaction. Frankly speaking, I prefer to communicate with an actual person rather than an ID number.

More simple user account design: Just need my actual name, e-mail and mobile phone number choice one, no password