<?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: User Interface Design: Complexity vs. Flexibility</title>
	<atom:link href="http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/</link>
	<description>Passionate about Startups and MicroISVs</description>
	<lastBuildDate>Tue, 07 Feb 2012 17:42:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-377</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 09 Feb 2007 16:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-377</guid>
		<description>I&#039;m talking about the user experience of the software.  XML is very flexible, and it may be simple for a software developer to understand, but what if I gave it to a business user and told them to edit it? I&#039;d have to create some kind of GUI editor on top of it that limits his options (thus reducing flexibility).  Adding tons of preset search parameters makes the software more flexible from a UI perspective - it allows a user to be more in control of the data they see.</description>
		<content:encoded><![CDATA[<p>I&#8217;m talking about the user experience of the software.  XML is very flexible, and it may be simple for a software developer to understand, but what if I gave it to a business user and told them to edit it? I&#8217;d have to create some kind of GUI editor on top of it that limits his options (thus reducing flexibility).  Adding tons of preset search parameters makes the software more flexible from a UI perspective &#8211; it allows a user to be more in control of the data they see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-376</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Thu, 08 Feb 2007 21:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-376</guid>
		<description>are talking about the software itself, or the user experience?  something highly configurable by the end user will be less flexible for the developer.  a single report may seem more flexible to the user, but its actually more code and more complexity they&#039;re seeing.  don&#039;t flexibility and simplicity often go hand-in-hand.  XML being an example.  by adding tons of preset search parameters as in your first example, aren&#039;t you really making the software itself less flexible?</description>
		<content:encoded><![CDATA[<p>are talking about the software itself, or the user experience?  something highly configurable by the end user will be less flexible for the developer.  a single report may seem more flexible to the user, but its actually more code and more complexity they&#8217;re seeing.  don&#8217;t flexibility and simplicity often go hand-in-hand.  XML being an example.  by adding tons of preset search parameters as in your first example, aren&#8217;t you really making the software itself less flexible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rwalling</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-375</link>
		<dc:creator>rwalling</dc:creator>
		<pubDate>Mon, 05 Feb 2007 20:08:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-375</guid>
		<description>Ilya,  Thanks for your feedback - you make a good point.  Thirty years ago I bet that car makers would have placed a set of toggle switches on the dash and expected you to remember them. This would not only be easier to design, but cheaper to build. This is how a lot of application developers approach application design - do what&#039;s easy to design and cheap to build.  So I do think complexity naturally increases as flexibility does, but there are ways around this tendency. But those ways require additional design work or additional constructions costs...or both. And that&#039;s the point of this post.  Finally, I don&#039;t think the converse is true; in other words, a project does not becomes more flexible anytime it&#039;s made more complex. Since my statement of an &quot;inverse relationship&quot; does indicate the converse to be true, I&#039;m going to remove that piece and leave it as the more simply stated:  &quot;...the more flexibility something offers, the more complex it tends to become.&quot;  Thanks for your insight,  Rob</description>
		<content:encoded><![CDATA[<p>Ilya,  Thanks for your feedback &#8211; you make a good point.  Thirty years ago I bet that car makers would have placed a set of toggle switches on the dash and expected you to remember them. This would not only be easier to design, but cheaper to build. This is how a lot of application developers approach application design &#8211; do what&#8217;s easy to design and cheap to build.  So I do think complexity naturally increases as flexibility does, but there are ways around this tendency. But those ways require additional design work or additional constructions costs&#8230;or both. And that&#8217;s the point of this post.  Finally, I don&#8217;t think the converse is true; in other words, a project does not becomes more flexible anytime it&#8217;s made more complex. Since my statement of an &#8220;inverse relationship&#8221; does indicate the converse to be true, I&#8217;m going to remove that piece and leave it as the more simply stated:  &#8220;&#8230;the more flexibility something offers, the more complex it tends to become.&#8221;  Thanks for your insight,  Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-374</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 05 Feb 2007 19:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-374</guid>
		<description>This reminds me of the old program PC Tools/PC Backup, back in the DOS days.  One of the menu bar headings was something like &quot;Complexity&quot; and the choices below were something like Simple/Medium/Advanced.  Of course, the default was simple.</description>
		<content:encoded><![CDATA[<p>This reminds me of the old program PC Tools/PC Backup, back in the DOS days.  One of the menu bar headings was something like &#8220;Complexity&#8221; and the choices below were something like Simple/Medium/Advanced.  Of course, the default was simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rwalling</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-373</link>
		<dc:creator>rwalling</dc:creator>
		<pubDate>Mon, 05 Feb 2007 19:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-373</guid>
		<description>Amit - I&#039;ve changed the wording to what you&#039;ve suggested in order to better map to an inverse relationship.</description>
		<content:encoded><![CDATA[<p>Amit &#8211; I&#8217;ve changed the wording to what you&#8217;ve suggested in order to better map to an inverse relationship.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-372</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Mon, 05 Feb 2007 19:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-372</guid>
		<description>Interesting read, but I think the inverse relationship is too simple of a theory.   Let&#039;s step outside the world of software development for a second and look at &#039;adjustable seats&#039; in your car. Some of the higher end models have a dozen adjustable settings - it&#039;s both a complex and flexible system. However, now assign each position a toggle and lay them out on the dash. Will you ever remember which is which? Probably not. But, if you lay them out in the shape of the seat itself, all of the sudden it becomes easy and simple. (presence of a natural mapping)  Complexity and flexibility are definitely not one to one. You can make a project more complex without making it flexible and vice versa.</description>
		<content:encoded><![CDATA[<p>Interesting read, but I think the inverse relationship is too simple of a theory.   Let&#8217;s step outside the world of software development for a second and look at &#8216;adjustable seats&#8217; in your car. Some of the higher end models have a dozen adjustable settings &#8211; it&#8217;s both a complex and flexible system. However, now assign each position a toggle and lay them out on the dash. Will you ever remember which is which? Probably not. But, if you lay them out in the shape of the seat itself, all of the sudden it becomes easy and simple. (presence of a natural mapping)  Complexity and flexibility are definitely not one to one. You can make a project more complex without making it flexible and vice versa.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-371</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Mon, 05 Feb 2007 19:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-371</guid>
		<description>You&#039;re probably better off stating &quot;The more flexibility something offers, the less simplistic it tends to become.&quot;  Which basically boils down to the same thing you are stating.</description>
		<content:encoded><![CDATA[<p>You&#8217;re probably better off stating &#8220;The more flexibility something offers, the less simplistic it tends to become.&#8221;  Which basically boils down to the same thing you are stating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-370</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Mon, 05 Feb 2007 19:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-370</guid>
		<description>http://en.wikipedia.org/wiki/Inverse_relationship  Usually an inverse relationship is where one value increases as another value decreases as the wikipedia definition states.  But, your example states &quot;the more flexibility something offers, the more complex it tends to become.&quot;  That looks like a direct relationship to me.</description>
		<content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/wiki/Inverse_relationship" rel="nofollow">http://en.wikipedia.org/wiki/Inverse_relationship</a>  Usually an inverse relationship is where one value increases as another value decreases as the wikipedia definition states.  But, your example states &#8220;the more flexibility something offers, the more complex it tends to become.&#8221;  That looks like a direct relationship to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rwalling</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-369</link>
		<dc:creator>rwalling</dc:creator>
		<pubDate>Mon, 05 Feb 2007 18:01:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-369</guid>
		<description>Babak - thanks for the input. Looks like I&#039;ll have to delve deeper into this topic.  Amit - Tell me more about how my use of inverse relationship is skewed.</description>
		<content:encoded><![CDATA[<p>Babak &#8211; thanks for the input. Looks like I&#8217;ll have to delve deeper into this topic.  Amit &#8211; Tell me more about how my use of inverse relationship is skewed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-368</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Mon, 05 Feb 2007 16:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-368</guid>
		<description>your use of inverse relationship here is a little skewed, but I think I understand the point you&#039;re trying to make.</description>
		<content:encoded><![CDATA[<p>your use of inverse relationship here is a little skewed, but I think I understand the point you&#8217;re trying to make.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: http://</title>
		<link>http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/comment-page-1/#comment-367</link>
		<dc:creator>http://</dc:creator>
		<pubDate>Mon, 05 Feb 2007 09:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarebyrob.com/2007/02/04/user-interface-design-complexity-versus-flexibility/#comment-367</guid>
		<description>I agree but you&#039;re stopping short of the real story here... that is, what were the elements of design and HCI that wordpress and gmail implemented that allowed them to reach such a lofty balance of simplicity and flexibility?  iow, how can we design solutions which cater to both the beginner (by being simple to use) and to the expert (by being flexible and configurable)?  I look forward to part 2 ;o)</description>
		<content:encoded><![CDATA[<p>I agree but you&#8217;re stopping short of the real story here&#8230; that is, what were the elements of design and HCI that wordpress and gmail implemented that allowed them to reach such a lofty balance of simplicity and flexibility?  iow, how can we design solutions which cater to both the beginner (by being simple to use) and to the expert (by being flexible and configurable)?  I look forward to part 2 ;o)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

