<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Account Sign-in &#8211; 8 Design Mistakes to Avoid</title>
	<atom:link href="http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 11 Feb 2012 08:11:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Bryan Owens</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-145552</link>
		<dc:creator>Bryan Owens</dc:creator>
		<pubDate>Sat, 07 Feb 2009 01:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-145552</guid>
		<description>Lately I&#039;ve been dealing with corporate career sites that require registrations for job submissions.

There&#039;s nothing worse than filling out a lengthy registration form, including resume, cover letter, etc. -- only to have it tell me on submission that my email address has already been used, presumably from an earlier application months or years earlier.

Easily solved by using inline validation of the email address as the first form field, along with the option of logging in using an existing account.  

Believe it or not, I&#039;ve actually seen some job-specific submission forms without an existing-account login option, which requires hunting around the site to find it, following by searching for the position again after login...[sigh]</description>
		<content:encoded><![CDATA[<p>Lately I&#8217;ve been dealing with corporate career sites that require registrations for job submissions.</p>
<p>There&#8217;s nothing worse than filling out a lengthy registration form, including resume, cover letter, etc. &#8212; only to have it tell me on submission that my email address has already been used, presumably from an earlier application months or years earlier.</p>
<p>Easily solved by using inline validation of the email address as the first form field, along with the option of logging in using an existing account.  </p>
<p>Believe it or not, I&#8217;ve actually seen some job-specific submission forms without an existing-account login option, which requires hunting around the site to find it, following by searching for the position again after login&#8230;[sigh]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Dowd</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144430</link>
		<dc:creator>Tim Dowd</dc:creator>
		<pubDate>Thu, 11 Dec 2008 16:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144430</guid>
		<description>Before validation, hints as to format are so helpful, such as dashes in a phone # or not. In fact, why doesn&#039;t the app parse instead of making the user do it? Separate fields for phone # parts are nice but some auto-tab to the next field while others don&#039;t and some forms auto-tab on some fields and not others...why? Some forms just validate to the first error, why not validate all fields and give feedback, rahter than user trial and error? After validation, hints as to what fields are bad and why are helpful, especially near the offending field.</description>
		<content:encoded><![CDATA[<p>Before validation, hints as to format are so helpful, such as dashes in a phone # or not. In fact, why doesn&#8217;t the app parse instead of making the user do it? Separate fields for phone # parts are nice but some auto-tab to the next field while others don&#8217;t and some forms auto-tab on some fields and not others&#8230;why? Some forms just validate to the first error, why not validate all fields and give feedback, rahter than user trial and error? After validation, hints as to what fields are bad and why are helpful, especially near the offending field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Kranz</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144428</link>
		<dc:creator>Jon Kranz</dc:creator>
		<pubDate>Thu, 11 Dec 2008 15:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144428</guid>
		<description>Good form design is not only pleasant, it&#039;s effective! But how do you balance good validation messages without sacrificing security against fraud or hacks (both of which are big problems we manage at my company)? 
Some validation messages may be good for users but can also help fraudsters or hackers. Captcha codes aren&#039;t enough. So what&#039;s a good way to go?</description>
		<content:encoded><![CDATA[<p>Good form design is not only pleasant, it&#8217;s effective! But how do you balance good validation messages without sacrificing security against fraud or hacks (both of which are big problems we manage at my company)?<br />
Some validation messages may be good for users but can also help fraudsters or hackers. Captcha codes aren&#8217;t enough. So what&#8217;s a good way to go?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Novey</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144414</link>
		<dc:creator>Grant Novey</dc:creator>
		<pubDate>Tue, 09 Dec 2008 22:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144414</guid>
		<description>If you&#039;ve ever forgot to fill out required field(s) in a form and then submitted it you should see some type of error telling you so. When I see forms using Javascript alert boxes telling the end-user what they forgot to fill out, it really annoys me. I&#039;ve seen forms move to using Ajax to inject the error messages directly onto the page instead of using an annoying alert box. Some web forms that I&#039;ve filled out use live validation giving the end-user immediate feedback before they click submit. This I like!</description>
		<content:encoded><![CDATA[<p>If you&#8217;ve ever forgot to fill out required field(s) in a form and then submitted it you should see some type of error telling you so. When I see forms using Javascript alert boxes telling the end-user what they forgot to fill out, it really annoys me. I&#8217;ve seen forms move to using Ajax to inject the error messages directly onto the page instead of using an annoying alert box. Some web forms that I&#8217;ve filled out use live validation giving the end-user immediate feedback before they click submit. This I like!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Ramlal</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144413</link>
		<dc:creator>Michael Ramlal</dc:creator>
		<pubDate>Tue, 09 Dec 2008 20:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144413</guid>
		<description>content thats erased out of a field after a validation warning thats anoying!</description>
		<content:encoded><![CDATA[<p>content thats erased out of a field after a validation warning thats anoying!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samantha LeVan</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144411</link>
		<dc:creator>Samantha LeVan</dc:creator>
		<pubDate>Tue, 09 Dec 2008 20:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144411</guid>
		<description>My pet peeve is unnecessarily long signup forms. If there&#039;s not enough incentive to continue, customers will back out before completing the process. There&#039;s little need for endless pages of signup fields. Focus on the priority items and let the rest be optional - later.</description>
		<content:encoded><![CDATA[<p>My pet peeve is unnecessarily long signup forms. If there&#8217;s not enough incentive to continue, customers will back out before completing the process. There&#8217;s little need for endless pages of signup fields. Focus on the priority items and let the rest be optional &#8211; later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Margaret</title>
		<link>http://www.uie.com/brainsparks/2008/12/09/uietips-sign-in-process/comment-page-1/#comment-144408</link>
		<dc:creator>Margaret</dc:creator>
		<pubDate>Tue, 09 Dec 2008 17:42:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=752#comment-144408</guid>
		<description>Another mistake I find very anoying is not to clarly indicate which fields are mandatory or even worse, make all the fields mandatory.</description>
		<content:encoded><![CDATA[<p>Another mistake I find very anoying is not to clarly indicate which fields are mandatory or even worse, make all the fields mandatory.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

