Examples of interactive design: registration and landing design

Recently in the Web site registration, landing, purchase, payment and other key aspects of the process optimization and interactive manuscript. These links are related to the Web site information architecture and are critical to the entire site. I am here to discuss registration and landing two processes.

>> Registration Process
1. Simplify the information that the user fills in when registering.
The basic logic of registration is that the less information users need to fill in, the higher the registration conversion rate. If you need to get more information about your users, you can get them gradually in the process of using the Web site. For example, when buying an operation, ask the user's name, telephone number, address and so on. In fact, according to my thinking, I think the only information that users need to provide when registering is the mailbox. I never thought the username was a useful field.

For the user information I think a better experience is: mailbox or mobile phone number as a login (login can be modified, reference Alipay), but also support OpenID (although it is most of the time is chicken ribs). After the successful registration of the user to provide users with a nickname field (and the nickname can also be modified, can refer to watercress).

Here to share a simple example of registration, is a foreign enterprise Social network very excellent site Yammer. The Yammer registration page has only one mailbox, and even the input password is placed after the mail is activated.

2. User verification process can be diversified
The majority of Web site registration requires mailbox authentication to activate. In fact, the verification information can be diversified: for example, SMS verification, by adding an IM robot robot to verify. Youa has added a text to verify OH. Of course, these validations are not as effective as the mail, as a way to expand it.

3. Some information should be masked to the user
Friends of the registration page due to historical problems, in the registration page has been 2 additional information, the first is the card number, password (that is, activecode information), the second referral. The next version of the revision, I will strongly push to remove these two messages. For activecode information, the referrer can be included in the code by hiding the IFRAME. And the referral is the user's name or the name of the referral person? is ambiguous.

>> Landing Process
First of all, users should not be forced to login operations, such as support visitors, purchase and so on.
In fact, the basic rating of the user: the first access to the site's new users, not yet logged in to the old user (test cookies to verify), the user has logged in (the following can be a further rating of logged-in users, such as ordinary logged-in users, paid users, etc.). It is important for the information architecture for which types of users to display what information.

Then, after these two logics, ask a few small questions to be discussed:
1. Home page to put the Login box, password box, or put the login link?
2. Which page should I jump to after landing? I think the current network of Friends of this design needs to be improved.