<?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: &#34;Pretty&#34; Software Applications</title>
	<atom:link href="http://josh.ev9.org/weblog/archives/407/feed" rel="self" type="application/rss+xml" />
	<link>http://josh.ev9.org/weblog/archives/407</link>
	<description>Interaction Design, User Experience, and the World at Large</description>
	<pubDate>Tue, 07 Feb 2012 13:45:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Hayes</title>
		<link>http://josh.ev9.org/weblog/archives/407/comment-page-1#comment-28886</link>
		<dc:creator>Ben Hayes</dc:creator>
		<pubDate>Fri, 03 Aug 2007 02:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://josh.ev9.org/weblog/archives/407#comment-28886</guid>
		<description>In some ways Agile Development seems to make the aesthetic 'visual design' element harder. If I know there are 7 tabs along the top of the page, I can factor that into my choice of layout grid, for example. If the next iteration adds 2 more tabs, my design may fall apart. If I'm aiming for perfection - trying to make it so that every little thing is balanced visually, it seems horrible to be told 'but it won't stay like this for longer than 2 weeks'.

Are we accepting that the best looking web app, for example, with complex interaction, will never look as good as the best designed, fixed size printed brochure?</description>
		<content:encoded><![CDATA[<p>In some ways Agile Development seems to make the aesthetic &#8216;visual design&#8217; element harder. If I know there are 7 tabs along the top of the page, I can factor that into my choice of layout grid, for example. If the next iteration adds 2 more tabs, my design may fall apart. If I&#8217;m aiming for perfection - trying to make it so that every little thing is balanced visually, it seems horrible to be told &#8216;but it won&#8217;t stay like this for longer than 2 weeks&#8217;.</p>
<p>Are we accepting that the best looking web app, for example, with complex interaction, will never look as good as the best designed, fixed size printed brochure?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc mcneill</title>
		<link>http://josh.ev9.org/weblog/archives/407/comment-page-1#comment-26813</link>
		<dc:creator>marc mcneill</dc:creator>
		<pubDate>Wed, 11 Jul 2007 09:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://josh.ev9.org/weblog/archives/407#comment-26813</guid>
		<description>Excellent post!  Nothing worse being brought in to advise on colours and fonts and layouts and usability when the fundamentals of the interaction design suck.  Nothing worse than ending an iteration with a showcase of working functionality ("it does what it says on the card") yet doesn't fit into the overall flow, the user journey...</description>
		<content:encoded><![CDATA[<p>Excellent post!  Nothing worse being brought in to advise on colours and fonts and layouts and usability when the fundamentals of the interaction design suck.  Nothing worse than ending an iteration with a showcase of working functionality (&#8221;it does what it says on the card&#8221;) yet doesn&#8217;t fit into the overall flow, the user journey&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shveta Aneja</title>
		<link>http://josh.ev9.org/weblog/archives/407/comment-page-1#comment-26811</link>
		<dc:creator>Shveta Aneja</dc:creator>
		<pubDate>Wed, 11 Jul 2007 08:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://josh.ev9.org/weblog/archives/407#comment-26811</guid>
		<description>You are not alone out there in the world where the majority think that the core job of a designer is to make things pretty and that the work of a designer is like a work of an artist!  But if the fundamentals of the product is broken, pretty design cannot save the product.

I think about it a lot, almost everyday - what can be done to change this thinking. Yes, we can do our part and do our best to advocate for what design process should be, but designers are not always the decision makers.  Its almost like designers and non-designers (people who think designing is prettying) work for the same company, have shared goals but speak completely different languages!</description>
		<content:encoded><![CDATA[<p>You are not alone out there in the world where the majority think that the core job of a designer is to make things pretty and that the work of a designer is like a work of an artist!  But if the fundamentals of the product is broken, pretty design cannot save the product.</p>
<p>I think about it a lot, almost everyday - what can be done to change this thinking. Yes, we can do our part and do our best to advocate for what design process should be, but designers are not always the decision makers.  Its almost like designers and non-designers (people who think designing is prettying) work for the same company, have shared goals but speak completely different languages!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Johnston</title>
		<link>http://josh.ev9.org/weblog/archives/407/comment-page-1#comment-26803</link>
		<dc:creator>Chris Johnston</dc:creator>
		<pubDate>Wed, 11 Jul 2007 05:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://josh.ev9.org/weblog/archives/407#comment-26803</guid>
		<description>All very good points, but it is amazing how the two -- getting the flow and usability of a site right and the beauty of the site -- merge together and complement one another. The more usable an interface becomes, the more beautiful it becomes; the two are directly linked.

"My point is that I will not (and cannot) make your system look nice unless the basic interaction part is already taken care of." My point is that as you fix the basic interaction the site will also improve aesthetically.

The reverse may not necessarily be true though. I have seen many "pretty" websites that were almost unusable. I put the word pretty in quotes because I actually think this is a skewed idea of what makes a pretty website. I personally think that, when defining a site as pretty, one must include the site's usability.</description>
		<content:encoded><![CDATA[<p>All very good points, but it is amazing how the two &#8212; getting the flow and usability of a site right and the beauty of the site &#8212; merge together and complement one another. The more usable an interface becomes, the more beautiful it becomes; the two are directly linked.</p>
<p>&#8220;My point is that I will not (and cannot) make your system look nice unless the basic interaction part is already taken care of.&#8221; My point is that as you fix the basic interaction the site will also improve aesthetically.</p>
<p>The reverse may not necessarily be true though. I have seen many &#8220;pretty&#8221; websites that were almost unusable. I put the word pretty in quotes because I actually think this is a skewed idea of what makes a pretty website. I personally think that, when defining a site as pretty, one must include the site&#8217;s usability.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

