User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm grappling with the user registration experience for my application.

I'm considering this model:

  1. User enters...

    • Username
    • Password
    • Password confirmation
    • Email address
  2. The app displays a message saying "Please check your email to complete your registration" and sends them an email sort of like...

    Hi username.

    It appears that you would like to register for Useful Web Application.

    If so, please click this link to complete your registration:
  3. They click the link and it takes them to a page saying, "Thanks. You're registered."

But I'm wondering if that second step is necessary.

I've noticed that Instapaper just registers you and logs you right in with no confirmation email.

Should I skip confirmation emails?

The main reason I want users' emails is so I can send a "reset password" link if they forget their login info.

(In case it's relevant, this app isn't a forum or a social site. It's more of a software as a service utility type of thing.)

share|improve this question

You need it for a simple reason so that you can ensure that people havent used someone else's email id to sign up for your service. Another reason for email verification is that people might identically enter their email wrong and an email verification steps helps them check that they had used the correct email to sign up.

An alternative approach you can use is to allow people to login once they sign up but keep a notification on top which informs them to verify their email addresses.

I dont recommend limiting functionality to ensure users verify their email,but you could keep a timer within which the user might verify his email to continue using the app.

Also provide them with a feature to update the email from your app just in case they accidentally entered the email wrong. This will ensure that they can update the email once signed in without having to recreate a new account.

share|improve this answer

I think users hate to verify their registration via email, I know I personally do.

For one thing, it's slower and takes more work. Users are lazy.

If this is done to make sure you receive a real email, an annoyed user can easily circumvent by using one of those temporary accounts (like mailinator). So it's pretty much useless..

If this is done to make sure the user hadn't misspelled their email, I think you can come up with better ways. For example, after registration show a quick message that registration was successful and that an email was sent to confirm that. Say that if the user did not receive a confirmation email, they should double check their email under their account settings. Of course, you should have an account settings page where users can view and edit their email address.

In addition, try to remember to login state (in a cookie for example if this is a web app) for at least 48 hours. So if the user did not receive a confirmation email, and they have closed the app, they would remain logged in and able to edit their email address in the account settings.

Another option is to ask for the email address twice (like the password), but I find this annoying as well.

I don't like the email validation messages (your email is not validated, and we will annoy you until it is), they are also super annoying.

If your service is paid for, I would encourage email validation since it should be a bit more robust in that case. But keep in mind that many payment gateways already rely on an email address (like PayPal) which you can assume to be correct without extra validation.

share|improve this answer

Another option is to separate validating the email from "completing registration".

You allow people to complete registration, but keep a reminder that the email address hasn't been validated.

That way users can register and use the site without being blocked or distracted by having to visit their email account (which isn't always possible in some contexts).

share|improve this answer

What about the user fills the registration inputs, clicks the Send or Register button and a message shows saying You are going to create a user with email + a button saying Confirm as a last step for the registration?

User would read the email again and confirm, instead of having to write twice their email or open their email app.

share|improve this answer

Unless you're really, really concerned about the authenticity of users' email addresses - skip the 2nd step.

If, for some reason, you want users to sign up with their real identities - again skip the 2nd step and use Facebook authentication or something similar instead.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.