<?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: If the Menu Fitts, We Must Acquit</title>
	<atom:link href="http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Sep 2010 01:37:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Zach Leatherman</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1964</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Wed, 05 May 2010 22:41:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1964</guid>
		<description>You can still have whitespace and an attractive looking click target.  The hover background doesn&#039;t necessarily need to be 1:1 with the click target. Won&#039;t apologize for being an engineer though :)</description>
		<content:encoded><![CDATA[<p>You can still have whitespace and an attractive looking click target.  The hover background doesn&#8217;t necessarily need to be 1:1 with the click target. Won&#8217;t apologize for being an engineer though :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arne Stephensson</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1956</link>
		<dc:creator>Arne Stephensson</dc:creator>
		<pubDate>Fri, 23 Apr 2010 17:59:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1956</guid>
		<description>In the examples you gave, the interface don&#039;t reach exactly to the left edge of the screen because the lack of whitespace would make things UGLY. Whitespace, like Fitt&#039;s Overrated Law, is also a huge usability factor.

There are two things you&#039;re placing at odds: the speed at which you can slam your cursor against the left edge of the screen, and the speed at which your eye can actually make out text better because of proper whitespace.

I don&#039;t think the two things have to be placed at odds, but if you say they have to be, then I&#039;d argue that adequate whitespace (as shown in the Wordpress and Gmail menus) is preferred over things like Fitt&#039;s Law.

I admire gratuitous use of whitespace in application and website design. I don&#039;t think most people are out to turn their users into the most efficient robots possible, shaving milliseconds off of the time that people can click the Spam folder in Gmail. Don&#039;t be such an engineer. Aesthetics is a huge part of usability. Your demo proves a point but... it&#039;s ugly. Fitt&#039;s Law might apply to more labor-intensive interfaces (like the menus at the top of the screen in Mac OS X, which are constantly being accessed), but when an application is just one of many, or when (as in your demo) it&#039;s just a blog with a few links, I think whitespace is a more important usability goal than Fitt&#039;s Law.</description>
		<content:encoded><![CDATA[<p>In the examples you gave, the interface don&#8217;t reach exactly to the left edge of the screen because the lack of whitespace would make things UGLY. Whitespace, like Fitt&#8217;s Overrated Law, is also a huge usability factor.</p>
<p>There are two things you&#8217;re placing at odds: the speed at which you can slam your cursor against the left edge of the screen, and the speed at which your eye can actually make out text better because of proper whitespace.</p>
<p>I don&#8217;t think the two things have to be placed at odds, but if you say they have to be, then I&#8217;d argue that adequate whitespace (as shown in the WordPress and Gmail menus) is preferred over things like Fitt&#8217;s Law.</p>
<p>I admire gratuitous use of whitespace in application and website design. I don&#8217;t think most people are out to turn their users into the most efficient robots possible, shaving milliseconds off of the time that people can click the Spam folder in Gmail. Don&#8217;t be such an engineer. Aesthetics is a huge part of usability. Your demo proves a point but&#8230; it&#8217;s ugly. Fitt&#8217;s Law might apply to more labor-intensive interfaces (like the menus at the top of the screen in Mac OS X, which are constantly being accessed), but when an application is just one of many, or when (as in your demo) it&#8217;s just a blog with a few links, I think whitespace is a more important usability goal than Fitt&#8217;s Law.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach Leatherman</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1880</link>
		<dc:creator>Zach Leatherman</dc:creator>
		<pubDate>Fri, 19 Feb 2010 23:30:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1880</guid>
		<description>Thanks guys.

Also, another thought: the &quot;infinite edge&quot; case doesn&#039;t quite apply for touchscreen interfaces.</description>
		<content:encoded><![CDATA[<p>Thanks guys.</p>
<p>Also, another thought: the &#8220;infinite edge&#8221; case doesn&#8217;t quite apply for touchscreen interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Shaw</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1875</link>
		<dc:creator>Daniel Shaw</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1875</guid>
		<description>Great post Zach. Very interesting observations.

I have two monitors and have one to the left of my main browsing window. Interesting how that infinite edge disappears when I have to consciously stop in that space.</description>
		<content:encoded><![CDATA[<p>Great post Zach. Very interesting observations.</p>
<p>I have two monitors and have one to the left of my main browsing window. Interesting how that infinite edge disappears when I have to consciously stop in that space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1873</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1873</guid>
		<description>IE8 (fullscreen mode) on Win7/Server 2008 R2 works on both cases (disabling the status bar).
Chromium (fullscreen mode) on Win7/Server 2008 R2 said some mean words and didn&#039;t work in either case.

After I went and did this I saw that you noted the fullscreen mode was out of scope, but I thought I&#039;d let you know the results anyway.

Thanks for the write-up. It&#039;s a very interesting thought - definitely something to consider when designing navigation. Multi-monitor situations are another interesting case for this, but I&#039;m guessing isn&#039;t common enough to stress over.</description>
		<content:encoded><![CDATA[<p>IE8 (fullscreen mode) on Win7/Server 2008 R2 works on both cases (disabling the status bar).<br />
Chromium (fullscreen mode) on Win7/Server 2008 R2 said some mean words and didn&#8217;t work in either case.</p>
<p>After I went and did this I saw that you noted the fullscreen mode was out of scope, but I thought I&#8217;d let you know the results anyway.</p>
<p>Thanks for the write-up. It&#8217;s a very interesting thought &#8211; definitely something to consider when designing navigation. Multi-monitor situations are another interesting case for this, but I&#8217;m guessing isn&#8217;t common enough to stress over.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Padolsey</title>
		<link>http://www.zachleat.com/web/2010/02/15/if-the-menu-fitts-we-must-acquit/comment-page-1/#comment-1872</link>
		<dc:creator>James Padolsey</dc:creator>
		<pubDate>Tue, 16 Feb 2010 18:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.zachleat.com/web/?p=542#comment-1872</guid>
		<description>Great post Zach! And an excellent point!

FWIW, Opera (I tested v. 10) seems to be compatible with this &quot;law&quot; too.</description>
		<content:encoded><![CDATA[<p>Great post Zach! And an excellent point!</p>
<p>FWIW, Opera (I tested v. 10) seems to be compatible with this &#8220;law&#8221; too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
