Design of the website user registration in the invitation test phase

Social design self (self)--invite beta version (private)

Issue Overview (Problem Summary)
The user wants to join a website that is currently in the invite testing phase.

Example (Example)

twine.com--the top left corner shows the site or the beta version. The registration form on the home page shows that the website is still in beta version, adding members to the website by invitation every day. Twine is no longer a beta.

When to use (using when)
1. When you allow users to register to join the online version of the site, you can use this mode;
2. You can use this mode when you allow a small number of users to develop your site by inviting other users to spread the virus (within control);

Solution Approach (Solution)
1. Clearly indicate that the website is still in beta stage;
2. Provide some features and benefits of the list or product demo, so that users know what to do after registration;
3. When required to register to receive information about the test version or the next version of the invitation information:
-Provide an email input box;
-Provide a user name input box;
-To have a confirmation page, let the user know that the site has received the registration request, and explain how much time will be given a feedback or an invitation.
-Send a confirmation email to the user to provide this email address to remind users when they can receive the invitation to join the beta version

4. When the user can be limited to invite some users to join the beta version of the time:
-a clear indication of how many invitations the user can send;
-record that the user has already used all the invitations and how many invitations are available;
-Allow users to customize the content of the invitation;
-Express to the invitees clearly some features and benefits of the site;

Logical basis (rationale)
Before the website was officially online, beta versions tested the social features of the site through a small number of people. From the beta version, so that the site has the opportunity to have a group from friends or family members of the seed, so as to avoid some cold start problems.

Special cases (Special Cases)
Earlier, the purpose of the beta was to require real user testing sites for a period of time--identifying bug--that could not be found by smaller groups of tests and then acting quickly or officially released, and then being accessible to larger audiences.

In today's web2.0 era, the ability to quickly publish Web apps, we see a growing number of websites with a beta logo and keep it forever.

This is often detrimental to the user and software development process, and the beta version undoubtedly involves the development of quality and product lifecycle. A beta release for a long time, which tells users that the site has a lot of bugs, and you may not take the time to fix them. This means that you don't care about the site and don't improve the functionality that causes the user to leave--why don't they just leave if that's the case?

Gmail has been a beta version from 2004 to now.

Since 04, Flick has also maintained a beta version for many years. Flickr is the gamma version from the end of 06 to the beginning of 07. This is the February 2007 Flickr home page.