0

My registration form requires 3 things: username, email, and password.

For login, the user can use either username or email (and password of course).

Thus, if the username is not necessary for logging in, would it be a good idea to cut it out of the registration form and just create a default username for the user (which they can change later in their profile settings)?

This would make the initial registration process simpler and faster, because the user only has to enter their email and password. However, I don't see any of the big sites doing this, so is there something "bad" about creating a default username "under water" for the user.

Is the user expectation of creating their own username (common practice) more important than the simplification of the initial registration?

2

Call it an Alias

I can enter email or username? The text box says Enter email/username; Should I enter both email and username? Uh... what was the username I entered while signing up? --- User

If the users of your site need to identify each other, then of course use a unique handle, but call it an alias, instead of username. And I would mainly encourage users to login via email, especially because users will make browsers remember the username, but forget when they occasionally try to log-in with another computer.


So let me get to the real question: If username is required for registration, but optional for login (email can be used instead), should it be part of the register form?

You say that "username is required for registration". If username is required then it should be a part of the registration form, for obvious reasons.

You can make username/alias optional in the registration form. In this scenario you can do two things.

  • Ask the user to choose a username/alias on their very first login, before actually doing anything with the site: I don't think this is very different from requiring a username/alias on the signup screen, because most users will login straight after they finish the signup process.
  • Create a username/alias "under water": There is one bad thing about this. Automatic usernames like (Ahem!) user1461424 are awful. That makes users feel like they are one of few million numbered cells in the matrix.

Heroku uses a nice scheme to default-name the apps users are creating. They are a combination of two random words, but are memorable and makes the user preserve them. (I once got "whispering beyond" for one of my apps). Here's one way you can do this: If you have a list of large number of adjectives and nouns, you can make nice usernames.

Adjectives                          Nouns
===================================================================
evil                                gargoyle
adorable                            trout
dizzy                               cat
scary                               butterfly
grumpy                              seashell

And you can combine the words and make usernames:

evil-trout
adorable-butterfly
grumpy-gargoyle

Well it always doesn't produce cool names, but that's one way of doing it. Try to come up with your own creative ideas for automatically generating usernames, rather than making user just a sequence number in the database.

  • Thanks! I definitely did not consider "fun" ways to auto-generate usernames, and was going to do some kind of sequence. Guess the big question is whether or not moving the username/alias beyond the initial registration form is worthwhile; it breaks common practice and user expectations, and even though it simplifies the initial registration, has it been shown to help with registration drop-off (can't find anything written on the subject)? – mrl Aug 13 '14 at 16:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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