<?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: Eyetracking: Cool, but how helpful?</title>
	<atom:link href="http://www.teehanlax.com/blog/2006/06/21/eyetracking-cool-but-how-helpful/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teehanlax.com/blog/2006/06/21/eyetracking-cool-but-how-helpful/</link>
	<description>Double True!</description>
	<lastBuildDate>Sat, 04 Sep 2010 15:07:35 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Travis</title>
		<link>http://www.teehanlax.com/blog/2006/06/21/eyetracking-cool-but-how-helpful/comment-page-1/#comment-29</link>
		<dc:creator>Travis</dc:creator>
		<pubDate>Fri, 23 Jun 2006 04:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.teehanlax.com/blog/?p=52#comment-29</guid>
		<description>We subconsciously grow accustomed to the conventional wisdoms of certain user interface aspects (ie. &quot;X&quot; means close or even scroll bars and their usage - sure, it&#039;s intuitive - these days).  See something enough times and you learn to accept it - plain and simple.
Consequently, there will always be those users who cause ripples in the way we see things.  Sometimes ripples bring forth design evolution, but more often than not ripples bring forth angry yells to stop rocking the boat (no animated Sherlock Holmes cursors, thanks for coming out though Microsoft Plus).

There are many design elements in use today that exist for no other reason than the fact that they&#039;re legacy elements passed on from generation to generation, version to version.  Microsoft got it right with the &#039;Start&#039; button.  Apple still gets it wrong by not having _all_ applications readily available in a direct &amp; simple way.
&quot;Click the finder icon then click applications in the left then find the program you&#039;re looking for by scrolling around awhile&quot; - Sure, for those who&#039;ve used a Mac it&#039;s easy - but many aren&#039;t going to think so, especially when they can visually identify a button labelled &#039;Start&#039; and quickly navigate to what they want just by moving their cursor over appropriately named categories (no clicking or excess scrolling).

The venerable David Barclay made a good point regarding the usefulness of Apple&#039;s Spotlight search: why&#039;m I only finding this out now?
Not exactly his words, but the message is all the same.
It&#039;s such a perfectly executed function yet it&#039;s so imperfectly implemented from an initiation perspective.  With most Macs having the screen real estate wide enough to accommodate it, why not build a spotlight search bar right into the top menu bar so all it would take would be the quick identification of an input field accompanied by a magnifying glass (or even a textual &quot;Search&quot;) submit button.  There would be no room for confusion.  Zero redundancy.
Conversely, give a gem of a tool like that to MS and you&#039;ll be getting &quot;helpful&quot; tooltips and hints promoting it for the rest of your life every time you even think of looking at the screen.
Regardless, I know I&#039;d rather have just a simple text field built into the menubar than having to click it or use a key combo to activate it.

In regards to web user interface design, just because N% are more inclined to read/click things on the left side of a 2-pane website layout still leaves room for X% to read/click things on the right.  Sure, content and aesthetics can be optimized or tweaked to accommodate the larger percentage&#039;s viewing habits, but everything in moderation... I definitely wouldn&#039;t stuff all my gold content into the left just because 55% are clicking left-pane content.  Otherwise, what becomes of the quality of content in the right-pane?

Heat maps are an interesting tool that really just confirm what many of us already know when it comes to design - we&#039;re trained and constantly training ourselves how to interpret today&#039;s visual interfaces and if somebody&#039;s going to wander off the beaten path of conventional wisdom, they&#039;d better do a damn good job at it or they&#039;ll just be remembered as that jerk who rocked the boat.</description>
		<content:encoded><![CDATA[	<p>We subconsciously grow accustomed to the conventional wisdoms of certain user interface aspects (ie. &#8220;X&#8221; means close or even scroll bars and their usage &#8211; sure, it&#8217;s intuitive &#8211; these days).  See something enough times and you learn to accept it &#8211; plain and simple.<br />
Consequently, there will always be those users who cause ripples in the way we see things.  Sometimes ripples bring forth design evolution, but more often than not ripples bring forth angry yells to stop rocking the boat (no animated Sherlock Holmes cursors, thanks for coming out though Microsoft Plus).</p>

	<p>There are many design elements in use today that exist for no other reason than the fact that they&#8217;re legacy elements passed on from generation to generation, version to version.  Microsoft got it right with the &#8216;Start&#8217; button.  Apple still gets it wrong by not having <em>all</em> applications readily available in a direct & simple way.<br />
&#8220;Click the finder icon then click applications in the left then find the program you&#8217;re looking for by scrolling around awhile&#8221; &#8211; Sure, for those who&#8217;ve used a Mac it&#8217;s easy &#8211; but many aren&#8217;t going to think so, especially when they can visually identify a button labelled &#8216;Start&#8217; and quickly navigate to what they want just by moving their cursor over appropriately named categories (no clicking or excess scrolling).</p>

	<p>The venerable David Barclay made a good point regarding the usefulness of Apple&#8217;s Spotlight search: why&#8217;m I only finding this out now?<br />
Not exactly his words, but the message is all the same.<br />
It&#8217;s such a perfectly executed function yet it&#8217;s so imperfectly implemented from an initiation perspective.  With most Macs having the screen real estate wide enough to accommodate it, why not build a spotlight search bar right into the top menu bar so all it would take would be the quick identification of an input field accompanied by a magnifying glass (or even a textual &#8220;Search&#8221;) submit button.  There would be no room for confusion.  Zero redundancy.<br />
Conversely, give a gem of a tool like that to MS and you&#8217;ll be getting &#8220;helpful&#8221; tooltips and hints promoting it for the rest of your life every time you even think of looking at the screen.<br />
Regardless, I know I&#8217;d rather have just a simple text field built into the menubar than having to click it or use a key combo to activate it.</p>

	<p>In regards to web user interface design, just because N% are more inclined to read/click things on the left side of a 2-pane website layout still leaves room for X% to read/click things on the right.  Sure, content and aesthetics can be optimized or tweaked to accommodate the larger percentage&#8217;s viewing habits, but everything in moderation&#8230; I definitely wouldn&#8217;t stuff all my gold content into the left just because 55% are clicking left-pane content.  Otherwise, what becomes of the quality of content in the right-pane?</p>

	<p>Heat maps are an interesting tool that really just confirm what many of us already know when it comes to design &#8211; we&#8217;re trained and constantly training ourselves how to interpret today&#8217;s visual interfaces and if somebody&#8217;s going to wander off the beaten path of conventional wisdom, they&#8217;d better do a damn good job at it or they&#8217;ll just be remembered as that jerk who rocked the boat.</p>
 ]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.teehanlax.com/blog/2006/06/21/eyetracking-cool-but-how-helpful/comment-page-1/#comment-27</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 22 Jun 2006 03:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.teehanlax.com/blog/?p=52#comment-27</guid>
		<description>I just want to add to Dave&#039;s post. I was really taken with eyetracking when I first saw the heat maps but I&#039;ve been asking the question &quot;How would this information change our design decisions&quot;. If we had this information would we really design any differently? Also to Jared Spool&#039;s point &quot;what does it really tell you&quot;? I can&#039;t quite reconcile those questions. 

I am open to learning more and don&#039;t want to write eyetracking off but something  these are nagging questions.</description>
		<content:encoded><![CDATA[	<p>I just want to add to Dave&#8217;s post. I was really taken with eyetracking when I first saw the heat maps but I&#8217;ve been asking the question &#8220;How would this information change our design decisions&#8221;. If we had this information would we really design any differently? Also to Jared Spool&#8217;s point &#8220;what does it really tell you&#8221;? I can&#8217;t quite reconcile those questions.</p>

	<p>I am open to learning more and don&#8217;t want to write eyetracking off but something  these are nagging questions.</p>
 ]]></content:encoded>
	</item>
</channel>
</rss>
