<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Simfatic Solutions Blog &#187; form design</title>
	<atom:link href="http://www.simfatic.com/blog/tag/form-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.simfatic.com/blog</link>
	<description>Updates on Simfatic Solutions</description>
	<lastBuildDate>Sat, 17 Dec 2011 07:20:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Evolving your form</title>
		<link>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/</link>
		<comments>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/#comments</comments>
		<pubDate>Sat, 03 Oct 2009 11:23:09 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Simfatic Forms]]></category>
		<category><![CDATA[form design]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=116</guid>
		<description><![CDATA[Some of the recent support requests made me think of this: how to make building complex forms easier? If you have used Simfatic Forms, you will immediately realize that Simfatic Forms makes it pretty quick to build a large form. Taken by this, users build a large form and get overwhelmed by the large set [...]]]></description>
			<content:encoded><![CDATA[<p>Some of the recent support requests made me think of this: how to make building complex forms easier? If you have used Simfatic Forms, you will immediately realize that Simfatic Forms makes it pretty quick to build a large form. Taken by this, users build a large form and get overwhelmed by the large set of input fields that they have to deal with in the later steps.</p>
<p>Here is how to develop your (big or small) form iteratively. The iterative approach is guaranteed to take half the complexity away.<br />
<span id="more-116"></span></p>
<h2>Start from a simple form</h2>
<p>Add the minimum number of fields to the form. Simfatic Forms provides you the flexibility of updating the form at any later point. So don&#8217;t worry about having the perfect form design in the first step itself.</p>
<h2>Designing calculation fields  or  validations without uploading the form</h2>
<p>The client side validations and calculation fields can be tested before installing the form on the webserver. One option is to use the preview feature. </p>
<p>Yet another option is to start with a &#8216;client side only&#8217; form first and add the server side options later. Here is how to do it:<br />
In the &#8216;Form General&#8217; page, in the &#8216;Form Processing&#8217; tab, choose the &#8216;Other&#8217; option for &#8216;Server side processing&#8217;. Leave the &#8216;action&#8217; field empty.<br />
<img src="http://www.simfatic.com/blog/wp-content/uploads/2009/09/general-form-props.png" alt="general-form-props" width="473" height="219" class="alignnone size-full wp-image-123" /><br />
Now you can preview the form in your browser (locally) as you develop the form ( Proceed to the &#8216;Generate Code&#8217; page and press the &#8216;Open the form&#8217; button.)</p>
<p>This &#8216;Client side first&#8217; method is best for forms with complex calculation fields or those with complex validations. You can build and test the form without installing the form on the web server each time.</p>
<p>Once the form design is ready, choose the &#8216;Simfatic Forms&#8217; form processor&#8217; option ( in the &#8216;Form processing options&#8217; tab) and proceed with designing the server side options.</p>
<h2>Choose the minimum options, install it and get the form running</h2>
<p>In the &#8216;form processing options&#8217; page choose one of the options ( like &#8216;send form submission by email&#8217; or &#8216;confirmation page&#8217; ) , install the form and see the form working. </p>
<h2>Iterate; add more fields and test again</h2>
<p>Now add more fields and more server side options. Make sure that the auto-generated templates (like the email template) are generated again. Re-install the form. Test the form again.</p>
<p>During the further iterations you can add more complexity: like adding a calculation field, changing the style of the form (the &#8216;look and feel page&#8217;) , saving to database and more.</p>
<h2>Keeping backups of your form design</h2>
<p>The form design you make using Simfatic Forms can be saved to an .fwz file (choose the file-&gt;Save menu item). It can often happen that after making some design changes you originally liked an earlier one. It is always good to keep intermittent backups of work in progress. This way if you want to roll back to an older design quickly.<br />
(This is true for any work in progress &#8211; like a document in progress or even a web page design in progress)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/simfatic-forms/116/evolving-your-form/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Before putting CAPTCHA on your next web form</title>
		<link>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/</link>
		<comments>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 11:33:45 +0000</pubDate>
		<dc:creator>prasanth</dc:creator>
				<category><![CDATA[Web Forms]]></category>
		<category><![CDATA[captcha]]></category>
		<category><![CDATA[form design]]></category>

		<guid isPermaLink="false">http://www.simfatic.com/blog/?p=82</guid>
		<description><![CDATA[CAPTCHA has become common part in almost any web form now-a-days. It has become increasingly difficult to decipher the code even for extra-ordinary humans ! There are several discussions on the usability issues of CAPTCHA (here are some more). A bad CAPTCHA can bring down the number of form submissions considerably. You may lose leads, [...]]]></description>
			<content:encoded><![CDATA[<p><a href='http://en.wikipedia.org/wiki/CAPTCHA'>CAPTCHA</a> has become common part in almost any web form now-a-days. It has become increasingly difficult to decipher the code even for extra-ordinary humans ! </p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-sample1.png" alt="captcha-sample" width="309" height="168" class="alignnone size-full wp-image-95" /><br />
<span id="more-82"></span><br />
There are several discussions on the <a href='http://blog.akismet.com/2009/02/04/make-commenting-easy/'>usability issues of CAPTCHA</a> (here are <a href='http://www.sitepoint.com/blogs/2008/06/18/reddits-flawed-captcha-adding-insult-to-injury/'>some</a> <a href='http://designbit.co.uk/2009/07/07/i-hate-captchas/'>more</a>). A bad CAPTCHA can <a href='http://www.seomoz.org/blog/captchas-affect-on-conversion-rates'>bring down the number of form submissions considerably</a>. You may lose leads, business, or contacts just because of an inappropriate CAPTCHA.</p>
<p>Let&#8217;s see when to use CAPTCHA (importantly, when <strong>not</strong> to use) and if at all required, how to make it easier for your visitors.</p>
<h2>Why CAPTCHA at all?</h2>
<p>CAPTCHA is for preventing bots from automatically submitting your form. These web bots are programs that leech through the web pages. When it finds a form, it fills the form with a spam message and submits.</p>
<p><strong>Why would someone send a web-bot to submit your form? What is their gain?</strong></p>
<ol>
<li>If the form submission appears immediately on a web page, the spammer can get back links to his website</li>
<p>The examples include blog comment forms and guest books. It is important that no form submission appears immediately on a web page. It will be an open invitation to spammers. Put a monitoring system in place.</p>
<li>If you are providing a free service (free email, free blogs) the spammer can create several thousand accounts</li>
<li>The spammer expects <em>you</em> to read his spam message</li>
<p>Rest of the forms fall in the third category. This category is the least attractive to the spammer since only you see the spam message! The chances of spam submissions to this category is the least. So why bother about CAPTCHA itself?
</ol>
<h2>Does your form really need a CAPTCHA?</h2>
<p>There is no reason to attach a CAPTCHA with every form that you get online. </p>
<ol>
<li>Design the form without CAPTCHA. Get it online!</li>
<li>You start getting form submissions. Take a note of the number of form submissions. (the conversion rate)</li>
<li> If you start getting spam submissions, attach a CAPTCHA.</li>
<li> Observe the drop in the number of genuine form submissions. Decide whether to keep the CAPTCHA </li>
</ol>
<p>If you have decided to keep the CAPTCHA, try the tips below to keep it easier for your visitors.</p>
<h2>Making a better CAPTCHA</h2>
<p>A good CAPTCHA will keep the form submission rate high while keeping the bots away. </p>
<div class='Para2'>
<h3>1. Avoid similar symbols in the CAPTCHA</h3>
<p>There are several characters that look similar. CAPTCHA, by nature is distorted. The similarity can cause confusion.</p>
<p>Examples:<br />
1(one) l(lowercase L) and I (uppercase i)<br />
0(zero) and O and o (lowercase O)<br />
4 and A<br />
8 and B<br />
6 and b</p>
<h3>2. Password field for Captcha?</h3>
<p>I don&#8217;t understand why some web forms have *Password field* for filling in the captcha code!</p>
<p>Password field, supposedly, is to prevent someone  seeing the entered text &#8216;over your shoulder&#8217;; right?</p>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-pwd.png" alt="captcha with password field" width="462" height="172" class="alignnone size-full wp-image-86" /></p>
<h3>3. Fill the form again? Oh No!</h3>
<p>Though this is very basic, I have seen this happening at least in a couple of forms.<br />
You fill the form, and manage to fill the CAPTCHA and submit. Bang! The form appears again and says the CAPTCHA code is wrong. That&#8217;s fine; but the entire form is cleared too!<br />
Use Ajax to validate CAPTCHA; never make the visitor fill the form again.</p>
<h3>4. Make it bigger</h3>
<p><img src="http://www.simfatic.com/blog/wp-content/uploads/2009/08/captcha-small.png" alt="too small captcha" width="303" height="117" class="alignnone size-full wp-image-87" /><br />
Bigger text is easier to decipher. The size of the characters doesn&#8217;t matter for the bots anyway. So make it larger.</p>
<h3>5. No Fancy fonts please!</h3>
<p>It is easier to decipher the code if the font is a familiar one.  Use a common, non-fancy font in the CAPTCHA</p>
<h3>6. Link to refresh the CAPTCHA.</h3>
<p>Always give an option to refresh the CAPTCHA. In case one code is difficult, your visitors can try another one.</p>
<h3>7. Keep it short</h3>
<p>A 6 character CAPTCHA code is reasonable while anything more than 10 is too much!
</p></div>
<p>Use CAPTCHA only when necessary. Even if you decided to have CAPTCHA, make it easier for your visitors.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.simfatic.com/blog/web-form/82/before-putting-captcha/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

