<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Login with email vs. username</title>
	<atom:link href="http://usabilitythoughts.com/login-with-email-vs-username.html/feed" rel="self" type="application/rss+xml" />
	<link>http://usabilitythoughts.com/login-with-email-vs-username.html</link>
	<description>content meets user</description>
	<lastBuildDate>Tue, 13 Dec 2011 11:48:53 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Moein</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-11940</link>
		<dc:creator>Moein</dc:creator>
		<pubDate>Tue, 13 Dec 2011 11:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-11940</guid>
		<description>Well I had to implement a login form and the model for it
So let me tell you if the programmer isn&#039;t lazy he can&#039;t easily resolve this problem
I did it this way
I added a check box after the email saying if the user wants to use a username and if the check box is not checked then I generate a unique random username and save it in the table
Then the user can login either with email or the username(just like twitter)
And he can always change the username as he likes
Like this you can have the both side happy right? ;)</description>
		<content:encoded><![CDATA[<p>Well I had to implement a login form and the model for it<br />
So let me tell you if the programmer isn&#8217;t lazy he can&#8217;t easily resolve this problem<br />
I did it this way<br />
I added a check box after the email saying if the user wants to use a username and if the check box is not checked then I generate a unique random username and save it in the table<br />
Then the user can login either with email or the username(just like twitter)<br />
And he can always change the username as he likes<br />
Like this you can have the both side happy right? <img src='http://usabilitythoughts.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Burke</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-10568</link>
		<dc:creator>Joe Burke</dc:creator>
		<pubDate>Thu, 15 Sep 2011 16:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-10568</guid>
		<description>I would say that email for login is the only appropriate method, but that does not remove, for some applications, the requirement of a username. The two should b e treated as separate entities used for different purposes.</description>
		<content:encoded><![CDATA[<p>I would say that email for login is the only appropriate method, but that does not remove, for some applications, the requirement of a username. The two should b e treated as separate entities used for different purposes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitchell Pilot</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-5638</link>
		<dc:creator>Mitchell Pilot</dc:creator>
		<pubDate>Thu, 02 Dec 2010 17:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-5638</guid>
		<description>I don&#039;t like email addresses as login IDs (although I see I am the outlier here). 

The original concept of using both a login ID and password (as opposed to just a password as was done in the early days) is that the ID can be a public identifier and only the password need be kept private.  Because of spam abuse, email addresses cannot be made public, thus making them a poor substitute for a user ID.  Adding a &quot;screen name&quot; while still using the email address to login further complicates what should be very simple:  your login ID is public, your password is private, your email address is a data item in your account (also private).

In my mind, the trend toward using email addresses as login identifiers is a touch of laziness on the part of website designers.  As you mentioned, it avoids the problem of checking for duplicates, and of storing an additional data item (the username) in the database.  It does this at the expense of using as a personal identifier something that was never meant to be that.

I will admit that I am biased because I use a disposable email service that assigns a different email address to every forum I visit; I have many email addresses and cannot remember any of them.  I can remember my username (for the few sites that let me use one).</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like email addresses as login IDs (although I see I am the outlier here). </p>
<p>The original concept of using both a login ID and password (as opposed to just a password as was done in the early days) is that the ID can be a public identifier and only the password need be kept private.  Because of spam abuse, email addresses cannot be made public, thus making them a poor substitute for a user ID.  Adding a &#8220;screen name&#8221; while still using the email address to login further complicates what should be very simple:  your login ID is public, your password is private, your email address is a data item in your account (also private).</p>
<p>In my mind, the trend toward using email addresses as login identifiers is a touch of laziness on the part of website designers.  As you mentioned, it avoids the problem of checking for duplicates, and of storing an additional data item (the username) in the database.  It does this at the expense of using as a personal identifier something that was never meant to be that.</p>
<p>I will admit that I am biased because I use a disposable email service that assigns a different email address to every forum I visit; I have many email addresses and cannot remember any of them.  I can remember my username (for the few sites that let me use one).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-5195</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 07 Oct 2010 18:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-5195</guid>
		<description>I dislike screen names, but what about the privacy and usability concerns associated with using an email address to log in? Can I set up an account using steve@apple.com? If so, I&#039;m not going to see communications about my account, and Steve&#039;s going to get spammed.

If the site requires me to verify that I own the email address, that introduces an extra step and a bunch of friction as my signup is interrupted by the need to go find the email and click its link.

Also, if the email address is a unique account identifier, can I plug other people&#039;s emails into the signup form and find out whether they have accounts already? Shouldn&#039;t that be private information?</description>
		<content:encoded><![CDATA[<p>I dislike screen names, but what about the privacy and usability concerns associated with using an email address to log in? Can I set up an account using <a href="mailto:steve@apple.com">steve@apple.com</a>? If so, I&#8217;m not going to see communications about my account, and Steve&#8217;s going to get spammed.</p>
<p>If the site requires me to verify that I own the email address, that introduces an extra step and a bunch of friction as my signup is interrupted by the need to go find the email and click its link.</p>
<p>Also, if the email address is a unique account identifier, can I plug other people&#8217;s emails into the signup form and find out whether they have accounts already? Shouldn&#8217;t that be private information?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dork</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-5181</link>
		<dc:creator>Dork</dc:creator>
		<pubDate>Fri, 01 Oct 2010 08:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-5181</guid>
		<description>i could think of some cons - 

1) if username is the same as the one in the email address, i.e. @.com etc, the user actually needs to type the whole email address, probably double the number of characters or more.

2) i generally don&#039;t like to be &quot;made&quot; to do something, and &quot;making the users use a real name&quot; probably won&#039;t work. i wouldn&#039;t put my real name anyway.

3) internet usernames - everyone has one. that&#039;s the whole thing about the internet. for one, i don&#039;t like to have to specify my actual full name, for anything really.

while i agree with the points you made, i think the best option is to give users a choice. some sites even go further to add in openID etc.</description>
		<content:encoded><![CDATA[<p>i could think of some cons &#8211; </p>
<p>1) if username is the same as the one in the email address, i.e. @.com etc, the user actually needs to type the whole email address, probably double the number of characters or more.</p>
<p>2) i generally don&#8217;t like to be &#8220;made&#8221; to do something, and &#8220;making the users use a real name&#8221; probably won&#8217;t work. i wouldn&#8217;t put my real name anyway.</p>
<p>3) internet usernames &#8211; everyone has one. that&#8217;s the whole thing about the internet. for one, i don&#8217;t like to have to specify my actual full name, for anything really.</p>
<p>while i agree with the points you made, i think the best option is to give users a choice. some sites even go further to add in openID etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandro Miguel Marques</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-5069</link>
		<dc:creator>Sandro Miguel Marques</dc:creator>
		<pubDate>Sun, 29 Aug 2010 01:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-5069</guid>
		<description>Adrian, I plenty agree with you.

The simple login db table

Id
NickName
Email
Passwd

The login auth read Email and Passwd fields and the name displayed could be the Nickname

Simply is the best</description>
		<content:encoded><![CDATA[<p>Adrian, I plenty agree with you.</p>
<p>The simple login db table</p>
<p>Id<br />
NickName<br />
Email<br />
Passwd</p>
<p>The login auth read Email and Passwd fields and the name displayed could be the Nickname</p>
<p>Simply is the best</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virusescu</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-35</link>
		<dc:creator>Virusescu</dc:creator>
		<pubDate>Sat, 18 Apr 2009 11:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-35</guid>
		<description>You&#039;re right admin.
Maybe I&#039;ll just state the obvious, but registering and logging-in doesn&#039;t have anything to do with data displayed on site.
If you deal with a big &quot;social network&quot; you can simply let the user choose his Display Name.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right admin.<br />
Maybe I&#8217;ll just state the obvious, but registering and logging-in doesn&#8217;t have anything to do with data displayed on site.<br />
If you deal with a big &#8220;social network&#8221; you can simply let the user choose his Display Name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razvan</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-16</link>
		<dc:creator>Razvan</dc:creator>
		<pubDate>Tue, 31 Mar 2009 11:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-16</guid>
		<description>I like the idea of using emails as login keys because, with the user&#039;s consent, you can tap into a public API from servives like Google or Yahoo and pick-up extra information that the user might need to fill in his profile page or that can help make your product more useful to him.</description>
		<content:encoded><![CDATA[<p>I like the idea of using emails as login keys because, with the user&#8217;s consent, you can tap into a public API from servives like Google or Yahoo and pick-up extra information that the user might need to fill in his profile page or that can help make your product more useful to him.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Overview on login forms &#124; Usability Thoughts</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-11</link>
		<dc:creator>Overview on login forms &#124; Usability Thoughts</dc:creator>
		<pubDate>Tue, 24 Mar 2009 10:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-11</guid>
		<description>[...] discussed the other day about the login with email vs. username and I came to the conclusion that it depends on the type of the application, if it&#8217;s social, [...]</description>
		<content:encoded><![CDATA[<p>[...] discussed the other day about the login with email vs. username and I came to the conclusion that it depends on the type of the application, if it&#8217;s social, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://usabilitythoughts.com/login-with-email-vs-username.html/comment-page-1#comment-9</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 18 Mar 2009 15:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=15#comment-9</guid>
		<description>it basically depends of the application and it&#039;s purpose</description>
		<content:encoded><![CDATA[<p>it basically depends of the application and it&#8217;s purpose</p>
]]></content:encoded>
	</item>
</channel>
</rss>

