<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Designing &#8220;Shorter&#8221; Web Forms</title>
	<link>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/</link>
	<description>The ultimate blog to Design vs Art</description>
	<pubDate>Wed, 07 Jan 2009 18:08:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Stever</title>
		<link>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5861</link>
		<author>Stever</author>
		<pubDate>Sat, 04 Oct 2008 18:45:29 +0000</pubDate>
		<guid>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5861</guid>
		<description>It was always a toss up for me as to whether a long form should be one page or split up into separate pages. Of course the long form looks daunting to fill out, but I was worried breaking it up into pages would mean added steps, more hoops to make the user jump through.

Besides your test users expressing more displeasure with a long form, it would be interesting to see the differences in form abandonment rates tested on real traffic.</description>
		<content:encoded><![CDATA[<p>It was always a toss up for me as to whether a long form should be one page or split up into separate pages. Of course the long form looks daunting to fill out, but I was worried breaking it up into pages would mean added steps, more hoops to make the user jump through.</p>
<p>Besides your test users expressing more displeasure with a long form, it would be interesting to see the differences in form abandonment rates tested on real traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexis Brion</title>
		<link>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5860</link>
		<author>Alexis Brion</author>
		<pubDate>Sat, 04 Oct 2008 10:48:26 +0000</pubDate>
		<guid>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5860</guid>
		<description>Hi Lowell, 

I wanted to make a point on how splitting a form could make it look shorter. If you are interested in web form design, let me pass you 2 articles I wrote before:

"Preventing Errors Filling Forms" on how making a web form easy to fill could encourage users to fill all the information you require. 
Read it here: http://www.designvsart.com/blog/2008/01/12/preventing-errors-filling-forms/

"Simple Forms Improve Usability" with another example of bad design. 
Read it here: http://www.designvsart.com/blog/2007/11/26/simple-forms-improve-usability/

Feel free to share another link!

Thanks!

Alex</description>
		<content:encoded><![CDATA[<p>Hi Lowell, </p>
<p>I wanted to make a point on how splitting a form could make it look shorter. If you are interested in web form design, let me pass you 2 articles I wrote before:</p>
<p>&#8220;Preventing Errors Filling Forms&#8221; on how making a web form easy to fill could encourage users to fill all the information you require.<br />
Read it here: <a href="http://www.designvsart.com/blog/2008/01/12/preventing-errors-filling-forms/" rel="nofollow">http://www.designvsart.com/blog/2008/01/12/preventing-errors-filling-forms/</a></p>
<p>&#8220;Simple Forms Improve Usability&#8221; with another example of bad design.<br />
Read it here: <a href="http://www.designvsart.com/blog/2007/11/26/simple-forms-improve-usability/" rel="nofollow">http://www.designvsart.com/blog/2007/11/26/simple-forms-improve-usability/</a></p>
<p>Feel free to share another link!</p>
<p>Thanks!</p>
<p>Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lowell</title>
		<link>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5859</link>
		<author>lowell</author>
		<pubDate>Fri, 03 Oct 2008 20:37:58 +0000</pubDate>
		<guid>http://www.designvsart.com/blog/2008/10/02/designing-shorter-web-forms/#comment-5859</guid>
		<description>where's the rest of the article? or was that 'it'?</description>
		<content:encoded><![CDATA[<p>where&#8217;s the rest of the article? or was that &#8216;it&#8217;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
