How do you see the third party landing

The last time I came across a problem I did not think of it was the choice of third-party registrations and local registrations. The reason is not as a problem before, because as a normal user, third party login / registration is simple and convenient, sometimes nothing more than some rogue applications rape my clockwork microblogging or leak information, but also directed at the convenience of it . But this time the problem has become a problem in the design of an application, the boss said to remove the local registration of the mouth, leaving only the mouth of a third party, suddenly all of a sudden, this is not the key to their own home to others Well, this is my own home Well! So I thought carefully ...

As far as I know now, there are four kinds of normal registration points, and the third one we currently use is to say the advantages and disadvantages respectively

· & Http: //www.aliyun.com/zixun/aggregation/37954.html "> nbsp; The first: the most traditional way to register, high registration threshold, easy to lose the user on the landing page

· The second: the app may be used in this very small, with no local ID left user, user behavior can not be tracked

· Third: After the third-party registration system defaults to the user an ID, the user may or may not be visible

Fourth: After the third-party registration user manually fill in an ID and can not repeat (this is my most annoying way, I feel like being cheated into the registration, even more than the direct registration trouble)

To say that, as long as the landing through a third party, on behalf of the user holding someone else's key into my house, once the key is taken away, the user will be gone.

The following from the user, the local app and the third party to talk about it

User's perspective

Third-party login to facilitate the daily life of the user's network, in an era inseparable from the network, every day face a different login screen, can have a simple landing method is very important. Third-party landing convenient, and a lot of information can be public information, and can be their own dynamic information in an app synchronized to each sns platform. So some lazy users may develop a kind of "an account of rivers and lakes," the heart.

But then again, no matter what the only way to deal with a capsid will certainly be in the gutter, such as your microblogging number was closed, your QQ number stolen, strains linked to the app can not log in , Register a new account, then before you recorded on the network life also returned to zero, at that time, how should you do?

Local client perspective

For local applications is nothing more than to simplify the landing process, lower registration threshold, access to massive new users. In the competition for users, to improve the user's conversion rate is to decide whether to highlight the important factor. The same thing has two sides, we use a third party to log in this way, to a degree dependent on a third party, in the know to see a very passionate article, that is about the use of the Three-way login and app application restrictions, the link URL is www.zhihu.com/question/19618841; Although some said the extreme point, but to some extent, app designers or investors a wake-up call, and For the kind of direct removal of the local registration of the app, but also should think about their app's future development, take care ah ~ ~ ~ Furthermore is the user ability to third party login hesitation, that is, on the privacy of the leak, we subconsciously Do not want to leak too much information in a casual app, here are two pictures

In summary, if only to retain third-party login, then for those who want to protect their privacy, may be more easily lost

Third-party perspective

In this view, third-party account looks like a big boss, just give you a good mouth can make you a good point, the mouth of a pinch, it is estimated you are not living well, and can continue very well to expand Its own user base. I have not thought of any potential downside to this binding for these big bosses. In this game of winning and losing by the number of users, a powerful third party looks like the winner forever.

Future Developments: Creating a New Way to Login, Simpler, More Authoritative, Not Dependent

So start thinking, in the end what kind of landing, the most suitable for a new app. Previously I thought, if each user as a unit, there is a unique ID, similar to fingerprints, ID numbers and other unique and authentic things, so that the virtual social network fully implemented in a very solid foundation , But this may require a large database and server support, and even involves a lot of political factors, just as the first proposed openID, but also requires a relative acceptance of the user process. The future world will be an era of Internet transmission of optoelectronic information. How to be truly credible in this virtual world will be an issue that we want to gradually accomplish and think about.

So for now, we can have any good ideas? Seeing that there is a brother who knows about it, it may be a good idea to set up a way to unlock the Jiugongge after logging in for the first time without having to type it again. Of course, we can innovate and expand the technology, such as fingerprints, pupils, face recognition, etc., if you want a very secure account and password, it is necessary: ​​passwords, iris, fingerprints (with body temperature) Just like the safe in the movie. Sounds like a distant, but who knows, this Internet age may change anything in a flash.

Recently saw this Email one-time login method, for everyone to see

(Turn) introduces one of the most simple to achieve, it is the United States programmer Ben Brown in (2012) July this year.

His approach is simple. When the user logs in, only one email address input box is displayed.

After the user enters the email address, the website sends an email to the address, which contains a login link. By clicking on this link, the user proves that he / she is indeed the owner of this email and is valid in order to log in.

Login link only valid for a period of time, but through the cookie, allowing users to log in for a long time. If the cookie fails, send another login link to the user's mailbox.

As the entire certification process, are completed by e-mail, completely realize "passwordless login", and the operation process is natural, easy to understand. More importantly, it uses the existing Email protocol, does not require server-side deployment of new code, with the best compatibility.

The main disadvantage is that it requires the user to view the email once more, which is a bit cumbersome. It is also not suitable for situations where a user can not open Email, for example, surfing the internet at a friend's home. Therefore, using its website, you must also deploy alternative logins.

To sum up, it is for the third party to log in. As far as the current situation is concerned, the individual still disagrees with leaving only the third-party registrations and hopes to bring some help to those in need.

Source Address: http://nothingnongyige.di......5/40047714127