<?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: Challenging the Status Quo: Audi Redesigned</title>
	<atom:link href="http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Mon, 20 May 2013 13:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Wuju</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8601</link>
		<dc:creator>Wuju</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8601</guid>
		<description><![CDATA[Yes, I completly support the Right Hand Nav. I have in many occassion argued and supported the use on Right Nav and this article gave me solid facts to support it in the future. Thanks.

My hypothesis why right nave is better are as follow;

1) It&#039;s better to use right nav to free up the priceless left restate for say content from What&#039;s New to the full body text. After all, our eyes read from left to right, so why would we put repeating element like a nav on the left. Left Nav people argue why would we want people to learn a new system when Left is the standard and a big usability No No. Quess what it doesn&#039;t seem to make a big difference in time as stated in the article.

2) Mouse movement plays a big role on how fast people navigate. Because the nature that the scroll bar is on the right, it is far faster and more user friendly for our mouse arrow to stay on the right if we employ Right Nav in our site. Its would reduce or mouse from travelling across the screen when we need to navigate (back and forth, back and forth). I would even argue that the majority of the content nav text or image links tends to be available after a paragraph say, &quot;Read More&quot; would end on the the better right half of the screen. So why not Right Nav.

That&#039;s just my 2 cents and thank you for reading it :)]]></description>
		<content:encoded><![CDATA[<p>Yes, I completly support the Right Hand Nav. I have in many occassion argued and supported the use on Right Nav and this article gave me solid facts to support it in the future. Thanks.</p>
<p>My hypothesis why right nave is better are as follow;</p>
<p>1) It&#8217;s better to use right nav to free up the priceless left restate for say content from What&#8217;s New to the full body text. After all, our eyes read from left to right, so why would we put repeating element like a nav on the left. Left Nav people argue why would we want people to learn a new system when Left is the standard and a big usability No No. Quess what it doesn&#8217;t seem to make a big difference in time as stated in the article.</p>
<p>2) Mouse movement plays a big role on how fast people navigate. Because the nature that the scroll bar is on the right, it is far faster and more user friendly for our mouse arrow to stay on the right if we employ Right Nav in our site. Its would reduce or mouse from travelling across the screen when we need to navigate (back and forth, back and forth). I would even argue that the majority of the content nav text or image links tends to be available after a paragraph say, &#8220;Read More&#8221; would end on the the better right half of the screen. So why not Right Nav.</p>
<p>That&#8217;s just my 2 cents and thank you for reading it <img src='http://www-boxesandarrows-com.zippykid.netdna-cdn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8602</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8602</guid>
		<description><![CDATA[I wonder if the two focus groupers did not like the right handed nav because they were left handed? Was this taken into account?]]></description>
		<content:encoded><![CDATA[<p>I wonder if the two focus groupers did not like the right handed nav because they were left handed? Was this taken into account?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8603</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8603</guid>
		<description><![CDATA[But regardless of the usability of the right hand nav, does moving it really communicate &quot;innovation&quot;?  

Websters says innovation is &quot;the introduction of something new&quot;.  

Right hand nav is nothing new.  It&#039;s just different than most, and relying upon positioning of navigation to communicate branding seems weak, at best.]]></description>
		<content:encoded><![CDATA[<p>But regardless of the usability of the right hand nav, does moving it really communicate &#8220;innovation&#8221;?  </p>
<p>Websters says innovation is &#8220;the introduction of something new&#8221;.  </p>
<p>Right hand nav is nothing new.  It&#8217;s just different than most, and relying upon positioning of navigation to communicate branding seems weak, at best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8604</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8604</guid>
		<description><![CDATA[The right hand nav is often a common problem.  We are trained (at least in western society) to look at pages left to right.  When something so critical as navigation is on the right side of a page, unless we read hebrew (right to left) it will of course cause UX problems.]]></description>
		<content:encoded><![CDATA[<p>The right hand nav is often a common problem.  We are trained (at least in western society) to look at pages left to right.  When something so critical as navigation is on the right side of a page, unless we read hebrew (right to left) it will of course cause UX problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: al</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8605</link>
		<dc:creator>al</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8605</guid>
		<description><![CDATA[&quot;Razorfish, Germany wanted to address the fact that users surf with different browser window sizes. We believed developing pages for one fixed size is fundamentally inappropriate for web design and ignores the basic flexibility of the medium.&quot; 
--
I find this statement interesting given that the Razorfish site is a fixed width site.  However, I must say that I liked the Audi site.  Although I prefer the nav to be on the left or top, where they have and how they use it seemed fine.  My one exception with the site is the search...it seems hidden (below the right hand nav) and contains some horrible tabs that hide some, as far as I can tell, pretty useless features (why, for example, do they hide the link to their &quot;Glossary&quot; in a tab located behind the search field???).]]></description>
		<content:encoded><![CDATA[<p>&#8220;Razorfish, Germany wanted to address the fact that users surf with different browser window sizes. We believed developing pages for one fixed size is fundamentally inappropriate for web design and ignores the basic flexibility of the medium.&#8221;<br />
&#8211;<br />
I find this statement interesting given that the Razorfish site is a fixed width site.  However, I must say that I liked the Audi site.  Although I prefer the nav to be on the left or top, where they have and how they use it seemed fine.  My one exception with the site is the search&#8230;it seems hidden (below the right hand nav) and contains some horrible tabs that hide some, as far as I can tell, pretty useless features (why, for example, do they hide the link to their &#8220;Glossary&#8221; in a tab located behind the search field???).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrés López</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8606</link>
		<dc:creator>Andrés López</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8606</guid>
		<description><![CDATA[Good move by RF...!

I see right hand navigation is a good way of closing off an interface, especially in left aligned non-liquid sites.

It also pushes the content ahead of  navigation, which in itself brings contextual browsing, something we are seeing less of nowadays.]]></description>
		<content:encoded><![CDATA[<p>Good move by RF&#8230;!</p>
<p>I see right hand navigation is a good way of closing off an interface, especially in left aligned non-liquid sites.</p>
<p>It also pushes the content ahead of  navigation, which in itself brings contextual browsing, something we are seeing less of nowadays.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lindsay Evans</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8607</link>
		<dc:creator>Lindsay Evans</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8607</guid>
		<description><![CDATA[&quot;A style sheet (XSLT) controls the three possible arrangements of modules for a given template depending on the user&#039;s browser size&quot;

----

Okay, I got rather excited at the prospect of a mainstream commercial site using client side XSLT, but upon viewing the source, all I could find was references to the XSL-FO namespace.

All of the &quot;jumping&quot; seems to be done via JavaScript (in particurlar the file &lt;a href=&quot;http://www.audi.com/include/js/dynscale.js,&quot; rel=&quot;nofollow&quot;&gt;http://www.audi.com/include/js/dynscale.js,&lt;/a&gt; which just seems to be swapping the content of various elements around). Still pretty neat, but not what I was expecting.]]></description>
		<content:encoded><![CDATA[<p>&#8220;A style sheet (XSLT) controls the three possible arrangements of modules for a given template depending on the user&#8217;s browser size&#8221;</p>
<p>&#8212;-</p>
<p>Okay, I got rather excited at the prospect of a mainstream commercial site using client side XSLT, but upon viewing the source, all I could find was references to the XSL-FO namespace.</p>
<p>All of the &#8220;jumping&#8221; seems to be done via JavaScript (in particurlar the file <a href="http://www.audi.com/include/js/dynscale.js," rel="nofollow"></a><a href="http://www.audi.com/include/js/dynscale.js" rel="nofollow">http://www.audi.com/include/js/dynscale.js</a>, which just seems to be swapping the content of various elements around). Still pretty neat, but not what I was expecting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Watson</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8608</link>
		<dc:creator>Paul Watson</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8608</guid>
		<description><![CDATA[RHN seems a natural and obvious progression to me. I find in most cases while reading content I have unconciously moved my cursor over to the RHS of the page. It is also easier to move to the right than to the left, sure only marginally, but then margins do count.

As for reading... Yes we read left to right, which is perfect for RHN. After reading an article your eyes most likely are on the RHS, ready to see the RHN and click a new topic/section.

And as pointed out RHN means content is more centered and prominent, a definite good thing.]]></description>
		<content:encoded><![CDATA[<p>RHN seems a natural and obvious progression to me. I find in most cases while reading content I have unconciously moved my cursor over to the RHS of the page. It is also easier to move to the right than to the left, sure only marginally, but then margins do count.</p>
<p>As for reading&#8230; Yes we read left to right, which is perfect for RHN. After reading an article your eyes most likely are on the RHS, ready to see the RHN and click a new topic/section.</p>
<p>And as pointed out RHN means content is more centered and prominent, a definite good thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sherlock_yoda</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8609</link>
		<dc:creator>sherlock_yoda</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8609</guid>
		<description><![CDATA[What I like about this article is that RazorFish took an &#039;experience&#039; or &#039;brand&#039; decision (i.e. put the navigation on the right-hand side in order to be distinctive / innovative), but *then* thoroughly user tested the decision.

I think this is a healthy direction - focus on the overall goals / branding/ experience and then thoroughly test anything new or unusual.  Don&#039;t just discount unusual ideas - they may work for a particular audience / context.

It was also good to see a reasonable sample size being used, and this sample being targeted.

I&#039;d use the term &#039;controlled innovation&#039; to describe this process.  Though, I agree with Mike that moving an interface element isn&#039;t really innovative, though it may be distinctive.

Sherlock soon to be married :0)]]></description>
		<content:encoded><![CDATA[<p>What I like about this article is that RazorFish took an &#8216;experience&#8217; or &#8216;brand&#8217; decision (i.e. put the navigation on the right-hand side in order to be distinctive / innovative), but *then* thoroughly user tested the decision.</p>
<p>I think this is a healthy direction &#8211; focus on the overall goals / branding/ experience and then thoroughly test anything new or unusual.  Don&#8217;t just discount unusual ideas &#8211; they may work for a particular audience / context.</p>
<p>It was also good to see a reasonable sample size being used, and this sample being targeted.</p>
<p>I&#8217;d use the term &#8216;controlled innovation&#8217; to describe this process.  Though, I agree with Mike that moving an interface element isn&#8217;t really innovative, though it may be distinctive.</p>
<p>Sherlock soon to be married :0)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Fleming</title>
		<link>http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8610</link>
		<dc:creator>Lee Fleming</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/challenging-the-status-quo-audi-redesigned/#comment-8610</guid>
		<description><![CDATA[When I built my first two or three sites way back in the days when I didn&#039;t know anything about usability other than how to make things work, I used right-hand navigation. It made sense to me since the scrollbar is on the right. RHN used to be pretty common on the web. I don&#039;t know when, or why, it almost completely disappeared.

Based on the usability results for RHN vs. LHN, I suspect that the location of the navs don&#039;t significantly affect usability one way or the other, as long as 1) the navs are visible, 2) it&#039;s clearly navigation &amp; not something else, and 3) navs are labeled properly (no mystery meat). 

It&#039;s interesting to see the resurrection of RHN. Though I highly doubt it serves the purpose of making Audi&#039;s site stand out from those of other carmakers: ooh, lookie, the navs are over here, this MUST be Audi&#039;s site. Yeah, right. Colors probably would make more of a difference - at present, when I see those grays it means I&#039;m at Audi, or BMW, or Mercedes, or Jaguar, or Porsche, or Lexus ...]]></description>
		<content:encoded><![CDATA[<p>When I built my first two or three sites way back in the days when I didn&#8217;t know anything about usability other than how to make things work, I used right-hand navigation. It made sense to me since the scrollbar is on the right. RHN used to be pretty common on the web. I don&#8217;t know when, or why, it almost completely disappeared.</p>
<p>Based on the usability results for RHN vs. LHN, I suspect that the location of the navs don&#8217;t significantly affect usability one way or the other, as long as 1) the navs are visible, 2) it&#8217;s clearly navigation &amp; not something else, and 3) navs are labeled properly (no mystery meat). </p>
<p>It&#8217;s interesting to see the resurrection of RHN. Though I highly doubt it serves the purpose of making Audi&#8217;s site stand out from those of other carmakers: ooh, lookie, the navs are over here, this MUST be Audi&#8217;s site. Yeah, right. Colors probably would make more of a difference &#8211; at present, when I see those grays it means I&#8217;m at Audi, or BMW, or Mercedes, or Jaguar, or Porsche, or Lexus &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
