Sorry that this thread is a little off topic, but I’m looking for some
varying opinions on the subject and I think this group has a breadth of
experience on this matter
A little background info… the registration process for a web
application I
am developing will be targeting those ages 13+ with the bulk of the
users
being in the 13-25 age range. We are in the process of developing the
sign
up/registration and we’re run into a kink on our team on whether or not
to
require an e-mail address during the process. An argument for not
requiring
e-mail during registration within our team (one I am arguing against) is
that not everybody has an e-mail address, so we shouldn’t require it.
But,
being in the MySpace generation, I’d imagine that the majority of this
demographic have at least one e-mail address they check on occasion.
However, I don’t have any hard stats on Internet users who don’t have
e-mail, but I’d imagine it to be very low, but this is only a guess.
Now, I am curios on people’s thoughts on requiring or not requiring an
e-mail address during the sign up process for a web application given
the
above demographic. I can see the pros for requiring one much more than
the
pros for not requiring one at all. I just see there being a nightmare if
somebody forgets their password, their log in ID, or something else
related
to their account. Now, if we don’t require that e-mail address, they are
in
a tough spot since they have been locked out of their account. So, if
they
wanted back in, we don’t have a way to send them information to get
information back. However, not requiring it… at least as far as I can
tell
only solves one thing, they don’t need an e-mail address. But, with
e-mail
being so ubiquitous now, is this even a problem? There are so many free
e-mail hosts, Hotmail, Gmail, Yahoo, just to name a few, that I don’t
really
see this being a problem. Is requiring an e-mail address a barrier to an
application’s adoption?
Any thoughts, examples, facts, you can provide are greatly appreciated.