Simplify sign-up chain

[Garbash]

Current chain:

• User fills signup form.
• Receive in the form a message to check their email
• Confirms verification email in his account.
• Goes to Email confirmed page.
• Goes to login page to fill credentials.
• Gets in the system

Simplified chain:

• User fills signup form.
• Receives in the form a message to check their email
• Confirms verification email in his account.
• Is now logged in.

[clemsos]

UX-wise, there is also downsides to this 1) Possible exposure to bots (as we don't use recaptcha). 2) UX : not making user familiar with login screen on first use.

Yes! To let the user test the registered username password combination.

Additionally we train the user how to sign in to our site. The next time the user visit our site, she/he know where to find sign in, and how it works.

When the user registers, she/he does it on free will to accomplish a task or access content. The motivation is high at that moment which make that moment perfect for training. There is a risk, however, that the user might feel that the process takes too long. The risk of a too long process stands in relation to the user needs and motivation. The less need and motivation the higher risk of an unsatisfactory user experience.

See more in this SO answer, esp. discussion in the comments

[clemsos]

This can be implemented like 1) user registration create a session where verified=false (block the access to UI despite being logged in) 2) then when the verification page has been visited it turns the session to verified=true which enable access to UI.