<?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>Strange Systems &#187; jakob nielsen</title>
	<atom:link href="http://www.strangesystems.com/blog/tag/jakob-nielsen/feed" rel="self" type="application/rss+xml" />
	<link>http://www.strangesystems.com</link>
	<description>Architecture. User Experience. Exploring the overlap of physical and virtual.</description>
	<lastBuildDate>Fri, 11 Jun 2010 15:12:35 +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>Progressive Disclosure</title>
		<link>http://www.strangesystems.com/blog/progressive-disclosure.html</link>
		<comments>http://www.strangesystems.com/blog/progressive-disclosure.html#comments</comments>
		<pubDate>Fri, 07 Dec 2007 12:52:42 +0000</pubDate>
		<dc:creator>namho</dc:creator>
				<category><![CDATA[user experience]]></category>
		<category><![CDATA[jakob nielsen]]></category>
		<category><![CDATA[ui design]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://blog.strangesystems.net/?p=35</guid>
		<description><![CDATA[Progressive disclosure is quickly becoming a staple in my user experience vocabulary. It&#8217;s one of those impressive words that causes people to say &#8220;ooh!&#8221;. It has an authority about it that seems to squash the ever-recurring user experience dilemma: how to fit complex functionality into limited screen real-estate. This is how Jakob Nielsen describes it [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.useit.com/alertbox/progressive-disclosure.html">Progressive disclosure</a> is quickly becoming a staple in my user experience vocabulary. It&#8217;s one of those impressive words that causes people to say &#8220;ooh!&#8221;. It has an authority about it that seems to squash the ever-recurring user experience dilemma: how to fit complex functionality into limited screen real-estate.</p>
<p>This is how Jakob Nielsen describes it in <a href="http://www.useit.com/alertbox/progressive-disclosure.html">his Alertbox column</a>:</p>
<blockquote><p>Progressive disclosure defers advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone.</p></blockquote>
<p>Progressive disclosure works wonderfully well with search engine interfaces, and Google has used this to its full advantage making it its trademark with its zen-like front page that only displays a search bar.</p>
<p>This also seems like an ideal solution for mobile handsets that are always suffering from increasing complexity but needs to fit all the functionality into a screen the size of a business card.</p>
<p>Not so fast. As with all seductive terms, one has to be cautious. It is not a silver bullet for UX woes. It does not provide license to forgo careful study of how users use devices and interfaces: what are the core set of features that should be displayed on the initial screen? How and when should the secondary screen with the advanced features be accessed?</p>
<p>Simplicity is always what interface designers strive for and user want. Simplicity is never simple, and certainly not an excuse to be lazy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.strangesystems.com/blog/progressive-disclosure.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
