<?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/"
		>
<channel>
	<title>Comments on: About Usability</title>
	<atom:link href="http://blog.incase.de/index.php/2009/01/08/about-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.incase.de/index.php/2009/01/08/about-usability/</link>
	<description>Sven's occasional log</description>
	<lastBuildDate>Mon, 23 Aug 2010 22:28:38 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sven</title>
		<link>http://blog.incase.de/index.php/2009/01/08/about-usability/comment-page-1/#comment-2506</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Fri, 09 Jan 2009 07:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=60#comment-2506</guid>
		<description>Come on, that was just an EXAMPLE. Something simple to illustrate what I was talking about: 
Do not disable a feature because you think it is too complicate for the average user, but instead hide it by default, giving an access path for those that want to use that feature.
By all means, if you think &quot;advanced options&quot; is the wrong term, use &quot;more options&quot; instead, or use even both: a &quot;more options&quot; for anything you deem to complicated for the beginner, but not too complicated for average users, while showing an &quot;advanced options&quot; button with the additional options revealed by &quot;more options&quot; allows to select debugging and really advanced options.</description>
		<content:encoded><![CDATA[<p>Come on, that was just an EXAMPLE. Something simple to illustrate what I was talking about:<br />
Do not disable a feature because you think it is too complicate for the average user, but instead hide it by default, giving an access path for those that want to use that feature.<br />
By all means, if you think &#8220;advanced options&#8221; is the wrong term, use &#8220;more options&#8221; instead, or use even both: a &#8220;more options&#8221; for anything you deem to complicated for the beginner, but not too complicated for average users, while showing an &#8220;advanced options&#8221; button with the additional options revealed by &#8220;more options&#8221; allows to select debugging and really advanced options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IanM</title>
		<link>http://blog.incase.de/index.php/2009/01/08/about-usability/comment-page-1/#comment-2504</link>
		<dc:creator>IanM</dc:creator>
		<pubDate>Fri, 09 Jan 2009 00:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=60#comment-2504</guid>
		<description>At last, someone else in the Linux community who finds the GIMP too much. And I have been using Linux since 1997 and work as an analyst programmer.

I like my UIs simple too, with the option to switch on more features if I need them AND understand them. I loathe interfaces that throw everything at me at once, leaving me overwhelmed by choice and giving me no clue where to start or how to do the simple things.

Keep the simple things simple, and let the complicated things be possible - that is good design.

By the way, maybe &quot;More options&quot; is a better prompt than &quot;Advanced options&quot;.</description>
		<content:encoded><![CDATA[<p>At last, someone else in the Linux community who finds the GIMP too much. And I have been using Linux since 1997 and work as an analyst programmer.</p>
<p>I like my UIs simple too, with the option to switch on more features if I need them AND understand them. I loathe interfaces that throw everything at me at once, leaving me overwhelmed by choice and giving me no clue where to start or how to do the simple things.</p>
<p>Keep the simple things simple, and let the complicated things be possible &#8211; that is good design.</p>
<p>By the way, maybe &#8220;More options&#8221; is a better prompt than &#8220;Advanced options&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peng&#8217;s links for Thursday, 8 January &#171; I&#8217;m Just an Avatar</title>
		<link>http://blog.incase.de/index.php/2009/01/08/about-usability/comment-page-1/#comment-2503</link>
		<dc:creator>Peng&#8217;s links for Thursday, 8 January &#171; I&#8217;m Just an Avatar</dc:creator>
		<pubDate>Thu, 08 Jan 2009 20:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=60#comment-2503</guid>
		<description>[...] Muller: About Usability. Another resident of Planet Debian has a great post that I think you guys should read. Sven had [...]</description>
		<content:encoded><![CDATA[<p>[...] Muller: About Usability. Another resident of Planet Debian has a great post that I think you guys should read. Sven had [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Buck</title>
		<link>http://blog.incase.de/index.php/2009/01/08/about-usability/comment-page-1/#comment-2502</link>
		<dc:creator>Joe Buck</dc:creator>
		<pubDate>Thu, 08 Jan 2009 18:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/?p=60#comment-2502</guid>
		<description>So, why is full-duplex printing an &quot;advanced option&quot;?   Using a label like &quot;advanced&quot; for such a thing will just tend to intimidate the new user away from the very choice she or he must make to do what needs to be done.</description>
		<content:encoded><![CDATA[<p>So, why is full-duplex printing an &#8220;advanced option&#8221;?   Using a label like &#8220;advanced&#8221; for such a thing will just tend to intimidate the new user away from the very choice she or he must make to do what needs to be done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
