<?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"
	>
<channel>
	<title>Comments on: UIEtips Article: Five Usability Challenges of Web-Based Applications</title>
	<atom:link href="http://www.uie.com/brainsparks/2007/12/04/uietips-article-five-usability-challenges-of-web-based-applications-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2007/12/04/uietips-article-five-usability-challenges-of-web-based-applications-2/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<pubDate>Fri,  9 Jan 2009 03:33:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Paul Willard</title>
		<link>http://www.uie.com/brainsparks/2007/12/04/uietips-article-five-usability-challenges-of-web-based-applications-2/#comment-97573</link>
		<dc:creator>Paul Willard</dc:creator>
		<pubDate>Tue, 04 Dec 2007 23:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/2007/12/04/uietips-article-five-usability-challenges-of-web-based-applications-2/#comment-97573</guid>
		<description>Challenge: Site visitors do not read.  This can be true for all but content web sites, but it is an especially important consideration for web applications.

Solution: Create a site that can convert whatever activity you are hoping your visitor/customer will accomplish without needing to read (much), while ensuring depth of information is available to those that want it.
- Color is key in design.  The bulk of your content and site (60%ish) should be a base color that is pretty neutral.  Think black or blue here.  30% should be your accent color which is used to divide sections of the page and highlight or frame logical places that contain attention.  And 10% should be the action color, reserved for wherever you want the user to click for "next".  Over-use of the action color or even the accent color is very distracting to web apps and hurts conversion.
- Accept greater back-end complexity to avoid error messages and simplify the front-end.  For example, when taking a dollar amount in a filed, accept "$", ",", "." and interpret them appropriately rather than presenting the user with an error message when they put a dollar sign ($) in front of the amount.  Even though you put a $ visual in front of the text input box to let them know they did not NEED to enter a dollar sign, if they enter it, accept it and move on.  Due to the scale affect mentioned in Jared's article, it is worth your time to develop robust input parsing rather than returning the dsu (dumb-sh*t user) error message.
- Develop and adhere to standards as much as possible.  Use a standard page title size, location, tone, and tense.  Have the standard action button, a standard action color highlighting what you want visitors to accomplish, put the button in a standard location (bottom right?) above the fold. Use standards to show required fields throughout your site, either footnoting or bolding required fields or optional fields depending on what will keep your interface simplest. Adhere to standard web page layouts which users have become accustomed to such as logo in upper left linking to corporate home page, utility navigation in upper right next to search input text box, footer nav with site terms, site map, and corporate non-consumer uses, top tab and/or left nav structure with breadcrumbing, etc.
- Create a header, footer and navigation which blends in as a single ignorable unit so as not to distract from whatever you are trying ot focus the visitor on.  Of course, navigation clarity is paramount, but you can design it in such a way that once a user has glanced at it and figured it out, it becomes like wallpaper on your site and only gets a visitor's attention when the visitor actively applies their attention to it.
- Create a way for users to get more information about fields if desired while maintaining the simplest application possible. A new web standard developing along these lines might be dashed underlines (half-hyperlinked?) for keywords with brief descriptions in rollover text and more extensive descriptions available in old school pop-up windows or web 2.0 foldouts.
- Allow configurability, but do it in a way that does not overcomplicate for the new and casual users of the site.  A good example here is the google search preferences settings.  There is quite a bit of back end complexity, configurability, and power available, but only a small hypertext link on the main page, not a control for every field in the output.  Balance this carefully, showing the coplexity only to those that want to find it and can handle it.</description>
		<content:encoded><![CDATA[<p>Challenge: Site visitors do not read.  This can be true for all but content web sites, but it is an especially important consideration for web applications.</p>
<p>Solution: Create a site that can convert whatever activity you are hoping your visitor/customer will accomplish without needing to read (much), while ensuring depth of information is available to those that want it.<br />
- Color is key in design.  The bulk of your content and site (60%ish) should be a base color that is pretty neutral.  Think black or blue here.  30% should be your accent color which is used to divide sections of the page and highlight or frame logical places that contain attention.  And 10% should be the action color, reserved for wherever you want the user to click for &#8220;next&#8221;.  Over-use of the action color or even the accent color is very distracting to web apps and hurts conversion.<br />
- Accept greater back-end complexity to avoid error messages and simplify the front-end.  For example, when taking a dollar amount in a filed, accept &#8220;$&#8221;, &#8220;,&#8221;, &#8220;.&#8221; and interpret them appropriately rather than presenting the user with an error message when they put a dollar sign ($) in front of the amount.  Even though you put a $ visual in front of the text input box to let them know they did not NEED to enter a dollar sign, if they enter it, accept it and move on.  Due to the scale affect mentioned in Jared&#8217;s article, it is worth your time to develop robust input parsing rather than returning the dsu (dumb-sh*t user) error message.<br />
- Develop and adhere to standards as much as possible.  Use a standard page title size, location, tone, and tense.  Have the standard action button, a standard action color highlighting what you want visitors to accomplish, put the button in a standard location (bottom right?) above the fold. Use standards to show required fields throughout your site, either footnoting or bolding required fields or optional fields depending on what will keep your interface simplest. Adhere to standard web page layouts which users have become accustomed to such as logo in upper left linking to corporate home page, utility navigation in upper right next to search input text box, footer nav with site terms, site map, and corporate non-consumer uses, top tab and/or left nav structure with breadcrumbing, etc.<br />
- Create a header, footer and navigation which blends in as a single ignorable unit so as not to distract from whatever you are trying ot focus the visitor on.  Of course, navigation clarity is paramount, but you can design it in such a way that once a user has glanced at it and figured it out, it becomes like wallpaper on your site and only gets a visitor&#8217;s attention when the visitor actively applies their attention to it.<br />
- Create a way for users to get more information about fields if desired while maintaining the simplest application possible. A new web standard developing along these lines might be dashed underlines (half-hyperlinked?) for keywords with brief descriptions in rollover text and more extensive descriptions available in old school pop-up windows or web 2.0 foldouts.<br />
- Allow configurability, but do it in a way that does not overcomplicate for the new and casual users of the site.  A good example here is the google search preferences settings.  There is quite a bit of back end complexity, configurability, and power available, but only a small hypertext link on the main page, not a control for every field in the output.  Balance this carefully, showing the coplexity only to those that want to find it and can handle it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
