<?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: Google&#8217;s Design Principles</title>
	<atom:link href="http://whitneyhess.com/blog/2008/04/28/googles-design-principles/feed/" rel="self" type="application/rss+xml" />
	<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/</link>
	<description>Improving the human experience one day at a time</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:53:46 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Sainsbury</title>
		<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/comment-page-1/#comment-1498</link>
		<dc:creator>Chris Sainsbury</dc:creator>
		<pubDate>Mon, 16 Jun 2008 11:50:48 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/?p=157#comment-1498</guid>
		<description>I think &#039;every millisecond counts&#039; is also relevant when it comes to user cognition as well as page loading speed. 

When designing interfaces it&#039;s often tempting to compromise ideas due to business, technical or artictic pressures - choosing one interface widget rather than another, for example.

I like &#039;every millisecond counts&#039; because it empahsises the fact that we should think very carefully before compromising when it comes to ease of use - the user&#039;s ability to understand the form or app as quickly as possible should be paramount.

Even if it only saves the user a millisecond, it&#039;s still worth doing and will make them enjoy the product more.</description>
		<content:encoded><![CDATA[<p>I think &#8216;every millisecond counts&#8217; is also relevant when it comes to user cognition as well as page loading speed. </p>
<p>When designing interfaces it&#8217;s often tempting to compromise ideas due to business, technical or artictic pressures &#8211; choosing one interface widget rather than another, for example.</p>
<p>I like &#8216;every millisecond counts&#8217; because it empahsises the fact that we should think very carefully before compromising when it comes to ease of use &#8211; the user&#8217;s ability to understand the form or app as quickly as possible should be paramount.</p>
<p>Even if it only saves the user a millisecond, it&#8217;s still worth doing and will make them enjoy the product more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinny</title>
		<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/comment-page-1/#comment-764</link>
		<dc:creator>Pinny</dc:creator>
		<pubDate>Thu, 01 May 2008 21:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/?p=157#comment-764</guid>
		<description>I think you hit it right on the head 

the ideas are clear and very important for anyone out there thinking of the customer 1st</description>
		<content:encoded><![CDATA[<p>I think you hit it right on the head </p>
<p>the ideas are clear and very important for anyone out there thinking of the customer 1st</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whitney</title>
		<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/comment-page-1/#comment-744</link>
		<dc:creator>whitney</dc:creator>
		<pubDate>Tue, 29 Apr 2008 15:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/?p=157#comment-744</guid>
		<description>&lt;a href=&quot;http://whitneyhess.com/blog/2008/04/googles-design-principles/#comment-743&quot; class=&quot;comment_link&quot; rel=&quot;nofollow&quot;&gt;Christina&lt;/a&gt;, you&#039;re right, I was making a big leap with #2. I was trying to swing the pendulum in the other direction to find where values end and design principles begin. 

&quot;Every pixel has a job to do&quot; certainly sounds like a design principle, but it&#039;s pretty vague and could be interpreted differently by different teams. Is that the point or should design principles be more directional? How concrete is too concrete that it&#039;s no longer a principle but a rule?</description>
		<content:encoded><![CDATA[<p><a href="http://whitneyhess.com/blog/2008/04/googles-design-principles/#comment-743" class="comment_link" rel="nofollow">Christina</a>, you&#8217;re right, I was making a big leap with #2. I was trying to swing the pendulum in the other direction to find where values end and design principles begin. </p>
<p>&#8220;Every pixel has a job to do&#8221; certainly sounds like a design principle, but it&#8217;s pretty vague and could be interpreted differently by different teams. Is that the point or should design principles be more directional? How concrete is too concrete that it&#8217;s no longer a principle but a rule?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: christina</title>
		<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/comment-page-1/#comment-743</link>
		<dc:creator>christina</dc:creator>
		<pubDate>Tue, 29 Apr 2008 13:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/?p=157#comment-743</guid>
		<description>There is a big difference between every millisecond counts and each page must load in under one second. At Yahoo search we said &quot;every pixel has a job to do&quot; to express similar obsessiveness with utility and speed. Once you reach one second you can rest, but if you are always striving to be faster/lighter you question every design element, and your job is never done.</description>
		<content:encoded><![CDATA[<p>There is a big difference between every millisecond counts and each page must load in under one second. At Yahoo search we said &#8220;every pixel has a job to do&#8221; to express similar obsessiveness with utility and speed. Once you reach one second you can rest, but if you are always striving to be faster/lighter you question every design element, and your job is never done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Wright</title>
		<link>http://whitneyhess.com/blog/2008/04/28/googles-design-principles/comment-page-1/#comment-736</link>
		<dc:creator>Brad Wright</dc:creator>
		<pubDate>Mon, 28 Apr 2008 19:46:17 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/?p=157#comment-736</guid>
		<description>&quot;Allow for universal accessibility&quot; isn&#039;t likely to be something Google will publicly say, as their own products fall somewhat short of the bar with regards to technical accessibility. It&#039;s definitely a noble and necessary thing to strive for for the rest of us, however.</description>
		<content:encoded><![CDATA[<p>&#8220;Allow for universal accessibility&#8221; isn&#8217;t likely to be something Google will publicly say, as their own products fall somewhat short of the bar with regards to technical accessibility. It&#8217;s definitely a noble and necessary thing to strive for for the rest of us, however.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.282 seconds -->
