<?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: UI Friction and Apple&#8217;s Front Row</title>
	<atom:link href="http://stealthisidea.com/articles/front-row-friction/feed/" rel="self" type="application/rss+xml" />
	<link>http://stealthisidea.com/articles/front-row-friction/</link>
	<description>Philip Haine&#039;s articles on Product Vision, Innovation and Design</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Philip Haine</title>
		<link>http://stealthisidea.com/articles/front-row-friction/comment-page-1/#comment-2578</link>
		<dc:creator>Philip Haine</dc:creator>
		<pubDate>Sun, 26 Jul 2009 18:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/articles/front-row-friction/#comment-2578</guid>
		<description>Nick, thanks for the clarification on press-and-hold of the Home button.

That is annoying that the text is always truncated.  It sounds like another example of an Apple design philosophy I call, &quot;deliberate oversimplification&quot; that violates Einstein&#039;s quote (&quot;Make things as simple as possible, but no simpler&quot;) for the sake of a clean look and the perception of simplicity, at the expense of true simplicity.</description>
		<content:encoded><![CDATA[<p>Nick, thanks for the clarification on press-and-hold of the Home button.</p>
<p>That is annoying that the text is always truncated.  It sounds like another example of an Apple design philosophy I call, &#8220;deliberate oversimplification&#8221; that violates Einstein&#8217;s quote (&#8220;Make things as simple as possible, but no simpler&#8221;) for the sake of a clean look and the perception of simplicity, at the expense of true simplicity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Harris</title>
		<link>http://stealthisidea.com/articles/front-row-friction/comment-page-1/#comment-2575</link>
		<dc:creator>Nick Harris</dc:creator>
		<pubDate>Sun, 26 Jul 2009 14:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/articles/front-row-friction/#comment-2575</guid>
		<description>This may be a change to how Front Row works in later versions of OS X, after all, the UI has changed. However, once launched with a push of the (MENU) button on the very simple Apple Remote, you can use the (PLAY/PAUSE) to descend its hierarchy, (MENU) click will as you say take you back one level, but (MENU) hold will take you &quot;home&quot; to the top level of the Front Row hierarchy. This also works with (ESCAPE) on the keyboard.

Apart from that small point, I very much liked your article. One of the things that particularly irritates me about Front Row is the way that the &quot;movie poster&quot; is large for a brief moment then scales back over the blurb that explains about the movie. This text is almost always curtailed due to the restricted amount of space it appears in. Perhaps, holding (PLAY/PAUSE) would get you a side-by-side view, where you could look at the poster and read the full details of the movie. (+) or (UP) and (-) or (DOWN) would scroll the details side, revealing reviews. There is no reason to force the user to exit Front Row to research opinion on the movie via a conventional web browser. Apple could quite easily cache summaries of reviews from respected sources. Clicking (PLAY/PAUSE) again could go even deeper to the full review. So, at one level you would have comparative ratings and the next you would have the text of the review itself. It could conceivably include &quot;talking head&quot; video reviews.</description>
		<content:encoded><![CDATA[<p>This may be a change to how Front Row works in later versions of OS X, after all, the UI has changed. However, once launched with a push of the (MENU) button on the very simple Apple Remote, you can use the (PLAY/PAUSE) to descend its hierarchy, (MENU) click will as you say take you back one level, but (MENU) hold will take you &#8220;home&#8221; to the top level of the Front Row hierarchy. This also works with (ESCAPE) on the keyboard.</p>
<p>Apart from that small point, I very much liked your article. One of the things that particularly irritates me about Front Row is the way that the &#8220;movie poster&#8221; is large for a brief moment then scales back over the blurb that explains about the movie. This text is almost always curtailed due to the restricted amount of space it appears in. Perhaps, holding (PLAY/PAUSE) would get you a side-by-side view, where you could look at the poster and read the full details of the movie. (+) or (UP) and (-) or (DOWN) would scroll the details side, revealing reviews. There is no reason to force the user to exit Front Row to research opinion on the movie via a conventional web browser. Apple could quite easily cache summaries of reviews from respected sources. Clicking (PLAY/PAUSE) again could go even deeper to the full review. So, at one level you would have comparative ratings and the next you would have the text of the review itself. It could conceivably include &#8220;talking head&#8221; video reviews.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reinventing the desktop (for real this time) &#8211; Part 1 &#171; brian will . net</title>
		<link>http://stealthisidea.com/articles/front-row-friction/comment-page-1/#comment-2567</link>
		<dc:creator>Reinventing the desktop (for real this time) &#8211; Part 1 &#171; brian will . net</dc:creator>
		<pubDate>Mon, 20 Jul 2009 06:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/articles/front-row-friction/#comment-2567</guid>
		<description>[...] Currently, much work is going into GUI toolkits to make it easy to add UI animations, such as having elements that slide around. The inevitable problem with animations, though, is that they introduce action delays and so must be kept very short, and yet the shorter the animation, the more the animation defeats its original intent, which is to convey to users where elements go to and come from. (See Philip Haine&#8217;s critique of Apple FrontRow) [...]</description>
		<content:encoded><![CDATA[<p>[...] Currently, much work is going into GUI toolkits to make it easy to add UI animations, such as having elements that slide around. The inevitable problem with animations, though, is that they introduce action delays and so must be kept very short, and yet the shorter the animation, the more the animation defeats its original intent, which is to convey to users where elements go to and come from. (See Philip Haine&#8217;s critique of Apple FrontRow) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Haine</title>
		<link>http://stealthisidea.com/articles/front-row-friction/comment-page-1/#comment-2130</link>
		<dc:creator>Philip Haine</dc:creator>
		<pubDate>Thu, 06 Sep 2007 15:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/articles/front-row-friction/#comment-2130</guid>
		<description>The &lt;strong&gt;dock on Mac OSX&lt;/strong&gt; also suffers from UI friction.  When the is set to &quot;auto-hide&quot; you can move the cursor to the screen&#039;s edge to reveal it.  Unfortunately it slides out when it appears, and not as snappily as you&#039;d like.  Switching apps is a high-frequency operation: the UI should be optimized for speed.</description>
		<content:encoded><![CDATA[<p>The <strong>dock on Mac OSX</strong> also suffers from UI friction.  When the is set to &#8220;auto-hide&#8221; you can move the cursor to the screen&#8217;s edge to reveal it.  Unfortunately it slides out when it appears, and not as snappily as you&#8217;d like.  Switching apps is a high-frequency operation: the UI should be optimized for speed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

