<?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: the value of UI consistency</title>
	<atom:link href="http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/feed/" rel="self" type="application/rss+xml" />
	<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/</link>
	<description></description>
	<lastBuildDate>Mon, 01 Mar 2010 15:49:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The lost art of user experience &#124; 创意纪</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-41</link>
		<dc:creator>The lost art of user experience &#124; 创意纪</dc:creator>
		<pubDate>Sun, 27 Jul 2008 11:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-41</guid>
		<description>[...] The tools available to us developers have evolved much in recent years, allowing us to create richer interfaces and interactions. With power comes responsibility - we need to apply discretion when using advanced techniques and tools, as to not confuse users. Breaking interface conventions by using new technologies where they are not needed is a mistake. [...]</description>
		<content:encoded><![CDATA[<p>[...] The tools available to us developers have evolved much in recent years, allowing us to create richer interfaces and interactions. With power comes responsibility &#8211; we need to apply discretion when using advanced techniques and tools, as to not confuse users. Breaking interface conventions by using new technologies where they are not needed is a mistake. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: techfounder &#187; The lost art of user experience</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-40</link>
		<dc:creator>techfounder &#187; The lost art of user experience</dc:creator>
		<pubDate>Sat, 26 Jul 2008 05:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-40</guid>
		<description>[...] The tools available to us developers have evolved much in recent years, allowing us to create richer interfaces and interactions. With power comes responsibility - we need to apply discretion when using advanced techniques and tools, as to not confuse users. Breaking interface conventions by using new technologies where they are not needed is a mistake. [...]</description>
		<content:encoded><![CDATA[<p>[...] The tools available to us developers have evolved much in recent years, allowing us to create richer interfaces and interactions. With power comes responsibility &#8211; we need to apply discretion when using advanced techniques and tools, as to not confuse users. Breaking interface conventions by using new technologies where they are not needed is a mistake. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Zúñiga</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-42</link>
		<dc:creator>Joshua Zúñiga</dc:creator>
		<pubDate>Tue, 24 Jul 2007 20:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-42</guid>
		<description>This is a good synopsis of what is a prevalent issue in web and console application development.  I find that the value UI consistency if often lost in what is the least difficult solution to implement.  Much like patching holes in a leaky ship rather than bringing her to dock.

I have found that what is good to consider, from planning and execution stages, is to run those solutions through an architectural and UI checklist.  It is equally important to ensure that the UI decisions do not violate design structure.  It is all about balance.

It seems the loudest point I read from this is to consider this as a part of the delivery to the customer.  A co-worker of mine, named Steve, claims, &quot;The UI IS the application!&quot;.  He is right . . . who ultimately uses the software we design?</description>
		<content:encoded><![CDATA[<p>This is a good synopsis of what is a prevalent issue in web and console application development.  I find that the value UI consistency if often lost in what is the least difficult solution to implement.  Much like patching holes in a leaky ship rather than bringing her to dock.</p>
<p>I have found that what is good to consider, from planning and execution stages, is to run those solutions through an architectural and UI checklist.  It is equally important to ensure that the UI decisions do not violate design structure.  It is all about balance.</p>
<p>It seems the loudest point I read from this is to consider this as a part of the delivery to the customer.  A co-worker of mine, named Steve, claims, &#8220;The UI IS the application!&#8221;.  He is right . . . who ultimately uses the software we design?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Pepple</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-43</link>
		<dc:creator>Steve Pepple</dc:creator>
		<pubDate>Thu, 31 May 2007 02:09:30 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-43</guid>
		<description>I enjoyed your thoughts, and refinement of Shebanow&#039;s post. I find linguistics apply to the problem, after considering you point.

The structure and conventions of application design are perhaps arbitrary, out-dated, and insufficient, but they are the closest thing we have to a useful, basic user language.

This said, I look forward to the grammar of application and web design evolving. As users use their desktop and the web for novel tasks, corresponding design solutions are important.</description>
		<content:encoded><![CDATA[<p>I enjoyed your thoughts, and refinement of Shebanow&#8217;s post. I find linguistics apply to the problem, after considering you point.</p>
<p>The structure and conventions of application design are perhaps arbitrary, out-dated, and insufficient, but they are the closest thing we have to a useful, basic user language.</p>
<p>This said, I look forward to the grammar of application and web design evolving. As users use their desktop and the web for novel tasks, corresponding design solutions are important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Higgins :: the uncanny valley of user interface design</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-49</link>
		<dc:creator>Bill Higgins :: the uncanny valley of user interface design</dc:creator>
		<pubDate>Thu, 17 May 2007 06:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-49</guid>
		<description>[...] a lesson here for software designers, and one that I&#8217;ve talked about recently - we must ensure that we design our applications to remain consistent with the environment in which [...]</description>
		<content:encoded><![CDATA[<p>[...] a lesson here for software designers, and one that I&#8217;ve talked about recently &#8211; we must ensure that we design our applications to remain consistent with the environment in which [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecosystems &#187; links for 2007-04-26</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-45</link>
		<dc:creator>tecosystems &#187; links for 2007-04-26</dc:creator>
		<pubDate>Thu, 26 Apr 2007 05:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-45</guid>
		<description>[...] Bill Higgins :: the value of UI consistency i concur (tags: BillHiggins UI consistency) [...]</description>
		<content:encoded><![CDATA[<p>[...] Bill Higgins :: the value of UI consistency i concur (tags: BillHiggins UI consistency) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Shebanow</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-47</link>
		<dc:creator>Andrew Shebanow</dc:creator>
		<pubDate>Tue, 24 Apr 2007 21:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-47</guid>
		<description>Good post. FWIW, the point I was trying to make wasn&#039;t that UI consistency was not worth working towards. Rather, I was trying to say that the goal is to have &quot;cognitive consistency&quot; with the user&#039;s expectations rather than requiring everyone to work from the same design rulebook. Thus its ok to tweak the way your UI works if users still &quot;get it&quot;, but on the other hand its bad to change your UI if it forces users to stop and think when performing an action. The web already gets this right.</description>
		<content:encoded><![CDATA[<p>Good post. FWIW, the point I was trying to make wasn&#8217;t that UI consistency was not worth working towards. Rather, I was trying to say that the goal is to have &#8220;cognitive consistency&#8221; with the user&#8217;s expectations rather than requiring everyone to work from the same design rulebook. Thus its ok to tweak the way your UI works if users still &#8220;get it&#8221;, but on the other hand its bad to change your UI if it forces users to stop and think when performing an action. The web already gets this right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-44</link>
		<dc:creator>Glen</dc:creator>
		<pubDate>Mon, 23 Apr 2007 18:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-44</guid>
		<description>Good points, Bill.  Perhaps you&#039;re planning on touching on this in a future post, but one of the most aggravating things I&#039;ve had to deal with in UI work is getting an accurate model of the end user&#039;s capabilities and expectations.  I have sat through way too many arguments between uber-geeks about what&#039;s the &quot;easiest&quot; way to do something in a UI, and of course neither of them are anywhere remotely close to what our end users wanted.  Geeks frequently forget that what&#039;s easy for them can be very, very difficult to understand for the average user.

Glen</description>
		<content:encoded><![CDATA[<p>Good points, Bill.  Perhaps you&#8217;re planning on touching on this in a future post, but one of the most aggravating things I&#8217;ve had to deal with in UI work is getting an accurate model of the end user&#8217;s capabilities and expectations.  I have sat through way too many arguments between uber-geeks about what&#8217;s the &#8220;easiest&#8221; way to do something in a UI, and of course neither of them are anywhere remotely close to what our end users wanted.  Geeks frequently forget that what&#8217;s easy for them can be very, very difficult to understand for the average user.</p>
<p>Glen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James  Governor</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-48</link>
		<dc:creator>James  Governor</dc:creator>
		<pubDate>Mon, 23 Apr 2007 13:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-48</guid>
		<description>I agree with you Bill. My thoughts on Shabanow&#039;s post here: http://redmonk.com/jgovernor/2007/04/12/ui-consistency-death-but-i-want-plain-text/</description>
		<content:encoded><![CDATA[<p>I agree with you Bill. My thoughts on Shabanow&#8217;s post here: <a href="http://redmonk.com/jgovernor/2007/04/12/ui-consistency-death-but-i-want-plain-text/" rel="nofollow">http://redmonk.com/jgovernor/2007/04/12/ui-consistency-death-but-i-want-plain-text/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Champion</title>
		<link>http://billhiggins.us/blog/2007/04/20/the-value-of-ui-consistency/comment-page-1/#comment-46</link>
		<dc:creator>Mike Champion</dc:creator>
		<pubDate>Sun, 22 Apr 2007 16:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://billhiggins.us/weblog/2007/04/20/the-value-of-ui-consistency/#comment-46</guid>
		<description>Good post on an interesting topic.

Couple thoughts:

- There is often a tradeoff between shortening the learning curve and putting power in the hands of experts. I&#039;ve been very impressed recently with the Adobe Lightroom UI, which breaks a lot of conventions (and it is cross-platform which can make convention following even more difficult). It is a complex app that has felt approachable for a novice like myself (but requires investment), and powerful enough for those who spend a lot of time working within it.

- The web has had a minimum of conventions for quite a while, and has been hampered by the lack of basic UI building blocks (tree controls, etc. etc.) that in part lead to a lot of experimentation. But because of the lack of adopted conventions (like color palettes, and File / Edit / View menus), the web has a chance to redefine some metaphors that are outdated. For example, one of my favorite features of Gmail is its auto-save feature, which still is not a widely employed technique. (IMHO webapps that collect lengthy information should auto-save, even if only to present a &quot;draft&quot; version later, so as not to lose lots of work.)

- As you mention, there are many newly forming web conventions like having a linked logo in the upper left that takes one &quot;home&quot; (even my parents expect this one). Or having links that are openable in a new tab/window, which some sites break by using JS where they should not. There is still an open frontier to make the web a far more usable and enjoyable place than it is today!</description>
		<content:encoded><![CDATA[<p>Good post on an interesting topic.</p>
<p>Couple thoughts:</p>
<p>- There is often a tradeoff between shortening the learning curve and putting power in the hands of experts. I&#8217;ve been very impressed recently with the Adobe Lightroom UI, which breaks a lot of conventions (and it is cross-platform which can make convention following even more difficult). It is a complex app that has felt approachable for a novice like myself (but requires investment), and powerful enough for those who spend a lot of time working within it.</p>
<p>- The web has had a minimum of conventions for quite a while, and has been hampered by the lack of basic UI building blocks (tree controls, etc. etc.) that in part lead to a lot of experimentation. But because of the lack of adopted conventions (like color palettes, and File / Edit / View menus), the web has a chance to redefine some metaphors that are outdated. For example, one of my favorite features of Gmail is its auto-save feature, which still is not a widely employed technique. (IMHO webapps that collect lengthy information should auto-save, even if only to present a &#8220;draft&#8221; version later, so as not to lose lots of work.)</p>
<p>- As you mention, there are many newly forming web conventions like having a linked logo in the upper left that takes one &#8220;home&#8221; (even my parents expect this one). Or having links that are openable in a new tab/window, which some sites break by using JS where they should not. There is still an open frontier to make the web a far more usable and enjoyable place than it is today!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
