<?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: The Importance of Conventions</title>
	<atom:link href="http://usabilityfriction.com/2008/11/28/the-importance-of-conventions/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilityfriction.com/2008/11/28/the-importance-of-conventions/</link>
	<description>Usability shouldn't be a drag</description>
	<lastBuildDate>Thu, 05 Aug 2010 14:50:25 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathan Pledger</title>
		<link>http://usabilityfriction.com/2008/11/28/the-importance-of-conventions/comment-page-1/#comment-121</link>
		<dc:creator>Nathan Pledger</dc:creator>
		<pubDate>Fri, 28 Nov 2008 09:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=302#comment-121</guid>
		<description>I agree. You learn a lot of conventions, and then when you design something yourself you have to remember the subconscious learning you have so you don&#039;t make mistakes. Some metaphors, icons and techniques are so discrete you don&#039;t realise you are using an established control technique. The &quot;triangle on it&#039;s side&quot; does everything from &quot;Play&quot; to &quot;Build and Run&quot; - either function it&#039;s purpose is pretty clear.

The iPhone. For a technologically inferior phone, this phone seems to have an unwarranted level of hype, which is typical of Jobs. I&#039;m willing to accept it&#039;s a preference thing, maybe people prefer the usability which is admittedly a key feature of a Mac (personal preference only, not that any other platform is fundamentally harder to use). But the volume control clearly weakens the &quot;usability&quot; card. If the screen is tall, tough, you need to be as clever in your UI design as you do when your makign tarty coverflow controls. They could of course put a nice, tactile rocker switch on the side of the device like every other phone has - which is physically re-inforced to prevent accidental holding down and consequent deafening.

@programx</description>
		<content:encoded><![CDATA[<p>I agree. You learn a lot of conventions, and then when you design something yourself you have to remember the subconscious learning you have so you don&#8217;t make mistakes. Some metaphors, icons and techniques are so discrete you don&#8217;t realise you are using an established control technique. The &#8220;triangle on it&#8217;s side&#8221; does everything from &#8220;Play&#8221; to &#8220;Build and Run&#8221; &#8211; either function it&#8217;s purpose is pretty clear.</p>
<p>The iPhone. For a technologically inferior phone, this phone seems to have an unwarranted level of hype, which is typical of Jobs. I&#8217;m willing to accept it&#8217;s a preference thing, maybe people prefer the usability which is admittedly a key feature of a Mac (personal preference only, not that any other platform is fundamentally harder to use). But the volume control clearly weakens the &#8220;usability&#8221; card. If the screen is tall, tough, you need to be as clever in your UI design as you do when your makign tarty coverflow controls. They could of course put a nice, tactile rocker switch on the side of the device like every other phone has &#8211; which is physically re-inforced to prevent accidental holding down and consequent deafening.</p>
<p>@programx</p>
]]></content:encoded>
	</item>
</channel>
</rss>
