<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: What&#8217;s in it for me?</title>
	<atom:link href="http://rowansimpson.com/2009/07/12/whats-in-it-for-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/</link>
	<description>Made in New Zealand from local and imported ingredients</description>
	<lastBuildDate>Tue, 14 Feb 2012 22:58:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10466</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Mon, 20 Jul 2009 07:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10466</guid>
		<description><![CDATA[I&#039;ve worked on a couple of CSS-ification projects.  The reduction in   the page size is never as much as you would expect (especially when   zipped).  But, yes, it would be interesting to see what difference   these design changes made in this case.  Does anybody have any numbers   on this? 

I don&#039;t think this change was motivated by the key numbers that Lance   mentioned - although he is right that they will be watching these   closely to ensure they are aware of any negative side-effects.  I   think this was about putting a foundation in place for future   changes.  We&#039;ll all have to wait for these to start to show up over   the coming months. 

Also, I agree that job satisfaction amongst the dev + design teams is   a good criteria.  This was certainly a big part of the motivation   behind the migration to .NET that I have written about here   previously, and wouldn&#039;t be surprised if that was again the case with   these changes. 

]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve worked on a couple of CSS-ification projects.  The reduction in   the page size is never as much as you would expect (especially when   zipped).  But, yes, it would be interesting to see what difference   these design changes made in this case.  Does anybody have any numbers   on this? </p>
<p>I don&#8217;t think this change was motivated by the key numbers that Lance   mentioned &#8211; although he is right that they will be watching these   closely to ensure they are aware of any negative side-effects.  I   think this was about putting a foundation in place for future   changes.  We&#8217;ll all have to wait for these to start to show up over   the coming months. </p>
<p>Also, I agree that job satisfaction amongst the dev + design teams is   a good criteria.  This was certainly a big part of the motivation   behind the migration to .NET that I have written about here   previously, and wouldn&#8217;t be surprised if that was again the case with   these changes. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10464</link>
		<dc:creator><![CDATA[Scott]]></dc:creator>
		<pubDate>Mon, 20 Jul 2009 03:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10464</guid>
		<description><![CDATA[Thanks for the reply Rowan. I had taken the meaning from your comment about the inmates running the asylum that you thought the HTML example you gave was crazy.

We can only speculate at the motivations and all of yours are along the lines of what I would&#039;ve asked. It&#039;d be interesting to have stats for page size pre and post change. CSS based layout is often a smaller page size but a much larger stylesheet size. However as the stylesheet is loaded less, it&#039;s a better deal in total. When done properly, the flexibility of CSS in terms of layout is excellent as you&#039;d well know.

To say I&#039;m surprised at the fixed width layout is an understatement but perhaps there&#039;s some jiggery pokery going on in the background that&#039;ll help future adjustments to this. 

But haven&#039;t we got to a point in screen sizes now where maximisinig is virtually worthless? Apple has been aware of this for a long time but PC users still seem to love maximising, me included. At what point does screen resolution actually hinder your website layout. 1024? 1280, 1600, 2000? I&#039;m running 2x19&quot; monitors and everything still feels okay. The next monitor I&#039;d likely purchase would be around 23-24&quot;. Would I really want a site then stretching that full width? I don&#039;t have the answer but would guess no. Something for browser manufacturers to be thinking about too.

No doubt as Lance concludes, the motivation was for better income. However, don&#039;t let job satisfaction be excluded from your list of criteria as the reason for the HTML change. If you get the best HTML&#039;ers in the country in 2009 and tell them they have to code in tables they&#039;re not likely to stick around.

As a side note your email notification doesn&#039;t seem to be working.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the reply Rowan. I had taken the meaning from your comment about the inmates running the asylum that you thought the HTML example you gave was crazy.</p>
<p>We can only speculate at the motivations and all of yours are along the lines of what I would&#8217;ve asked. It&#8217;d be interesting to have stats for page size pre and post change. CSS based layout is often a smaller page size but a much larger stylesheet size. However as the stylesheet is loaded less, it&#8217;s a better deal in total. When done properly, the flexibility of CSS in terms of layout is excellent as you&#8217;d well know.</p>
<p>To say I&#8217;m surprised at the fixed width layout is an understatement but perhaps there&#8217;s some jiggery pokery going on in the background that&#8217;ll help future adjustments to this. </p>
<p>But haven&#8217;t we got to a point in screen sizes now where maximisinig is virtually worthless? Apple has been aware of this for a long time but PC users still seem to love maximising, me included. At what point does screen resolution actually hinder your website layout. 1024? 1280, 1600, 2000? I&#8217;m running 2&#215;19&#8243; monitors and everything still feels okay. The next monitor I&#8217;d likely purchase would be around 23-24&#8243;. Would I really want a site then stretching that full width? I don&#8217;t have the answer but would guess no. Something for browser manufacturers to be thinking about too.</p>
<p>No doubt as Lance concludes, the motivation was for better income. However, don&#8217;t let job satisfaction be excluded from your list of criteria as the reason for the HTML change. If you get the best HTML&#8217;ers in the country in 2009 and tell them they have to code in tables they&#8217;re not likely to stick around.</p>
<p>As a side note your email notification doesn&#8217;t seem to be working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Haylock</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10452</link>
		<dc:creator><![CDATA[Mark Haylock]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 10:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10452</guid>
		<description><![CDATA[@Rowan
Somewhat amusing that you would question the usefulness of tableless layout and then link to 456 Berea Steet... Johansson would most definitely disagree you.

i.e. &lt;a href=&quot;http://www.456bereastreet.com/archive/200601/failed_redesigns_use_web_standards_or_dont_bother_redesigning/&quot; rel=&quot;nofollow&quot;&gt;Failed redesigns: Use web standards or don’t bother redesigning&lt;/a&gt; ;)

I like the idea that if you&#039;re going to do it, do it right. But then I am a perfectionist, for all the good and bad that does me!

And I think producing great html/css/js is only possible if all your developers know how to produce great html/css/js (i.e. they have to care), and I get the impression that it&#039;s still pretty hard to hire/train that into a team (or to justify doing so). Not that I&#039;ve tried.

@Adam
I like the way you think :) On the bizarre id&#039;s... I wouldn&#039;t be surprised if they were the spawn of ASP.NET. But then I haven&#039;t worked with ASP.NET for a few years, maybe that sort of thing isn&#039;t an issue anymore?]]></description>
		<content:encoded><![CDATA[<p>@Rowan<br />
Somewhat amusing that you would question the usefulness of tableless layout and then link to 456 Berea Steet&#8230; Johansson would most definitely disagree you.</p>
<p>i.e. <a href="http://www.456bereastreet.com/archive/200601/failed_redesigns_use_web_standards_or_dont_bother_redesigning/" rel="nofollow">Failed redesigns: Use web standards or don’t bother redesigning</a> ;)</p>
<p>I like the idea that if you&#8217;re going to do it, do it right. But then I am a perfectionist, for all the good and bad that does me!</p>
<p>And I think producing great html/css/js is only possible if all your developers know how to produce great html/css/js (i.e. they have to care), and I get the impression that it&#8217;s still pretty hard to hire/train that into a team (or to justify doing so). Not that I&#8217;ve tried.</p>
<p>@Adam<br />
I like the way you think :) On the bizarre id&#8217;s&#8230; I wouldn&#8217;t be surprised if they were the spawn of ASP.NET. But then I haven&#8217;t worked with ASP.NET for a few years, maybe that sort of thing isn&#8217;t an issue anymore?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10451</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 09:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10451</guid>
		<description><![CDATA[Some random related bits and pieces...

From Hacker News:
&lt;a href=&quot;http://news.ycombinator.com/item?id=704605&quot; rel=&quot;nofollow&quot;&gt;Do sites using tables for latyouts have an advantage over W3C compliant sites?&lt;/a&gt;

Interesting debate, and sort of the same point that I was trying to make in my previous comment.

From 456 Berea St:
&lt;a href=&quot;http://www.456bereastreet.com/archive/200611/resolution_vs_browser_size_vs_fixed_or_adaptive_width/&quot; rel=&quot;nofollow&quot;&gt;Resolution vs. Browser Size vs. Fixed or Adaptive Width&lt;/a&gt;

Check out some of the articles linked here, they all point out that the key thing is not screen size (as reported by most analytics tools( but browser window size - i.e. the width of the actual area where pages are rendered (which seems to be mostly speculation).  I know I for one don&#039;t have my browser maximised on the large screen I use.]]></description>
		<content:encoded><![CDATA[<p>Some random related bits and pieces&#8230;</p>
<p>From Hacker News:<br />
<a href="http://news.ycombinator.com/item?id=704605" rel="nofollow">Do sites using tables for latyouts have an advantage over W3C compliant sites?</a></p>
<p>Interesting debate, and sort of the same point that I was trying to make in my previous comment.</p>
<p>From 456 Berea St:<br />
<a href="http://www.456bereastreet.com/archive/200611/resolution_vs_browser_size_vs_fixed_or_adaptive_width/" rel="nofollow">Resolution vs. Browser Size vs. Fixed or Adaptive Width</a></p>
<p>Check out some of the articles linked here, they all point out that the key thing is not screen size (as reported by most analytics tools( but browser window size &#8211; i.e. the width of the actual area where pages are rendered (which seems to be mostly speculation).  I know I for one don&#8217;t have my browser maximised on the large screen I use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10450</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 08:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10450</guid>
		<description><![CDATA[@Lance:

Those are the key things, but I don&#039;t think they are the motive.  Of course they will be watching to make sure that none of those numbers tank, but I don&#039;t expect that will happen.

I think the motive was to setup the design to better accommodate future design changes (I don&#039;t know exactly how you measure whether or not that was &quot;achieved&quot;).  So, I guess we look forward to those?]]></description>
		<content:encoded><![CDATA[<p>@Lance:</p>
<p>Those are the key things, but I don&#8217;t think they are the motive.  Of course they will be watching to make sure that none of those numbers tank, but I don&#8217;t expect that will happen.</p>
<p>I think the motive was to setup the design to better accommodate future design changes (I don&#8217;t know exactly how you measure whether or not that was &#8220;achieved&#8221;).  So, I guess we look forward to those?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lance</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10449</link>
		<dc:creator><![CDATA[lance]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 06:57:19 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10449</guid>
		<description><![CDATA[The biggest reasons for change are of course increased listings, sales and income. 

The success or otherwise of the redesign will be unknown to us outsiders (though if we see it revert we will have our suspicions). 
Internally it will quickly be reflected in the daily stats, the stats for each step in the core processes and, something we can see, in the number of listings at any one time.

I have yet to have a good look at it. Perhaps the blandness is to blame.]]></description>
		<content:encoded><![CDATA[<p>The biggest reasons for change are of course increased listings, sales and income. </p>
<p>The success or otherwise of the redesign will be unknown to us outsiders (though if we see it revert we will have our suspicions).<br />
Internally it will quickly be reflected in the daily stats, the stats for each step in the core processes and, something we can see, in the number of listings at any one time.</p>
<p>I have yet to have a good look at it. Perhaps the blandness is to blame.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10446</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 21:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10446</guid>
		<description><![CDATA[@Scott

My question is not whether the HTML is right or wrong (how do you tell that?)  My question is whether it&#039;s really an improvement over what came before.

I understand the cost of making this change, I just don&#039;t understand the benefits.

Some common reasons that might be used to justify this sort of change (some of which I&#039;ve used myself, to be fair):


&lt;strong&gt;Speed&lt;/strong&gt; (as a result of smaller page sizes and better caching) - How much smaller are the pages following the change?

&lt;strong&gt;Accessibility&lt;/strong&gt; - Was it tested before and after?  What improvements, specifically?
&lt;strong&gt;Easier to read&lt;/strong&gt; - What difference does this make?  Presumably it would be easier to make changes to the code if it&#039;s easier to read.  Any way to measure this?
&lt;strong&gt;Separation of data and layout&lt;/strong&gt; - Again, this sounds more like a means of achieving a benefit than a benefit in and of itself.  What does separation afford?  And can we really claim they are separate if the mark-up is full of redundant div tags and browser hacks
&lt;strong&gt;Support on different devices&lt;/strong&gt; (e.g. mobile phones) - Perhaps?  Was this something that was broken with the old mark-up?
&lt;strong&gt;Search Engine Optimisation&lt;/strong&gt; - As I&#039;ve previously mentioned here &lt;a href=&quot;http://rowansimpson.com/2007/05/30/designing-for-blind-users/&quot; rel=&quot;nofollow&quot;&gt;the most important visitor to your site is blind&lt;/a&gt;, so this seems a good reason.  But, again, how do you measure this?  Increased pages indexed by Google?  Better click-thru rates?
&lt;strong&gt;Future Proofing&lt;/strong&gt; - See Adam&#039;s comments re: HTML5
&lt;strong&gt;Better browser support&lt;/strong&gt; - Really?  The code seems to be full of hacks to support the existing set of browsers that people currently use


Are there other reasons I&#039;m missing?

Unless there is a clear reason, which can be measured afterwards, then my suspicion is raised.
 
@Adam:

I&#039;m pleased to hear that HTML5 is catching on.  God forbid that developers would be interested in using a standard that is actually widely supported by browsers that normal people use! ;-)]]></description>
		<content:encoded><![CDATA[<p>@Scott</p>
<p>My question is not whether the HTML is right or wrong (how do you tell that?)  My question is whether it&#8217;s really an improvement over what came before.</p>
<p>I understand the cost of making this change, I just don&#8217;t understand the benefits.</p>
<p>Some common reasons that might be used to justify this sort of change (some of which I&#8217;ve used myself, to be fair):</p>
<p><strong>Speed</strong> (as a result of smaller page sizes and better caching) &#8211; How much smaller are the pages following the change?</p>
<p><strong>Accessibility</strong> &#8211; Was it tested before and after?  What improvements, specifically?<br />
<strong>Easier to read</strong> &#8211; What difference does this make?  Presumably it would be easier to make changes to the code if it&#8217;s easier to read.  Any way to measure this?<br />
<strong>Separation of data and layout</strong> &#8211; Again, this sounds more like a means of achieving a benefit than a benefit in and of itself.  What does separation afford?  And can we really claim they are separate if the mark-up is full of redundant div tags and browser hacks<br />
<strong>Support on different devices</strong> (e.g. mobile phones) &#8211; Perhaps?  Was this something that was broken with the old mark-up?<br />
<strong>Search Engine Optimisation</strong> &#8211; As I&#8217;ve previously mentioned here <a href="http://rowansimpson.com/2007/05/30/designing-for-blind-users/" rel="nofollow">the most important visitor to your site is blind</a>, so this seems a good reason.  But, again, how do you measure this?  Increased pages indexed by Google?  Better click-thru rates?<br />
<strong>Future Proofing</strong> &#8211; See Adam&#8217;s comments re: HTML5<br />
<strong>Better browser support</strong> &#8211; Really?  The code seems to be full of hacks to support the existing set of browsers that people currently use</p>
<p>Are there other reasons I&#8217;m missing?</p>
<p>Unless there is a clear reason, which can be measured afterwards, then my suspicion is raised.</p>
<p>@Adam:</p>
<p>I&#8217;m pleased to hear that HTML5 is catching on.  God forbid that developers would be interested in using a standard that is actually widely supported by browsers that normal people use! ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10444</link>
		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 07:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10444</guid>
		<description><![CDATA[Oops, some HTML was stripped out... I&#039;ll see if I can get this to render right...

&lt;title id=&quot;SiteTitle_Title&quot;&gt;]]></description>
		<content:encoded><![CDATA[<p>Oops, some HTML was stripped out&#8230; I&#8217;ll see if I can get this to render right&#8230;</p>
<p>&lt;title id=&#8221;SiteTitle_Title&#8221;&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10442</link>
		<dc:creator><![CDATA[Adam]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 07:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10442</guid>
		<description><![CDATA[It was a bit of a surprise when I checked decided to check out the Auckland apartment market listings the other night from London... I saw the new design and wondered how out of the loop I was; &quot;how long has this been here?&quot;.

One thing I didn&#039;t like was the de-emphasis of the Motoring/Property/Auction sections. The graphics for those used to be quite easy to scan for, but now they&#039;re replaced by those generic coloured boxes, which seem a bit abstract and require a bit of cognitive effort (Don&#039;t Make Me Think).

Code wise there&#039;s some curious bits: &quot;&quot; for instance. I can&#039;t imagine what the ID&#039;s used for?

There&#039;s still a lot of JS in the HEAD as well. I wonder how performance tuned it&#039;s been.

And XHTML? Bah! It&#039;s all HTML5 now, baby. Must be time for a redesign... so behind the times. We&#039;ve all just had the epiphany that HTML was as semantic as XHTML after all.]]></description>
		<content:encoded><![CDATA[<p>It was a bit of a surprise when I checked decided to check out the Auckland apartment market listings the other night from London&#8230; I saw the new design and wondered how out of the loop I was; &#8220;how long has this been here?&#8221;.</p>
<p>One thing I didn&#8217;t like was the de-emphasis of the Motoring/Property/Auction sections. The graphics for those used to be quite easy to scan for, but now they&#8217;re replaced by those generic coloured boxes, which seem a bit abstract and require a bit of cognitive effort (Don&#8217;t Make Me Think).</p>
<p>Code wise there&#8217;s some curious bits: &#8220;&#8221; for instance. I can&#8217;t imagine what the ID&#8217;s used for?</p>
<p>There&#8217;s still a lot of JS in the HEAD as well. I wonder how performance tuned it&#8217;s been.</p>
<p>And XHTML? Bah! It&#8217;s all HTML5 now, baby. Must be time for a redesign&#8230; so behind the times. We&#8217;ve all just had the epiphany that HTML was as semantic as XHTML after all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10439</link>
		<dc:creator><![CDATA[Scott]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 06:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10439</guid>
		<description><![CDATA[Agree regarding colour comments. It&#039;s too sparse.

Gutted that they have animated ads. Cue ad blocker.

What&#039;s wrong with that HTML? Looks like good inheritance based CSS to me. The HTML comments are probably due to IE6 borking whitespace and are a necessary evil. The fact they&#039;re empty otherwise would probably mean they&#039;re for presentation, likely as corner boxes. We&#039;ll get those with CSS3, so about 6 years time. In the mean time that&#039;s a whole lot better than tables with rounded corners surely! Semantically, it makes sense, they mean nothing.]]></description>
		<content:encoded><![CDATA[<p>Agree regarding colour comments. It&#8217;s too sparse.</p>
<p>Gutted that they have animated ads. Cue ad blocker.</p>
<p>What&#8217;s wrong with that HTML? Looks like good inheritance based CSS to me. The HTML comments are probably due to IE6 borking whitespace and are a necessary evil. The fact they&#8217;re empty otherwise would probably mean they&#8217;re for presentation, likely as corner boxes. We&#8217;ll get those with CSS3, so about 6 years time. In the mean time that&#8217;s a whole lot better than tables with rounded corners surely! Semantically, it makes sense, they mean nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10438</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 03:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10438</guid>
		<description><![CDATA[Via Twitter &lt;a href=&quot;http://twitter.com/ajobbins&quot; rel=&quot;nofollow&quot;&gt;@ajobbins&lt;/a&gt; reminded me of this excellent example of Fire &amp; motion:


&lt;a href=&quot;http://rowan.wordpress.com/files/2009/07/kevo.gif&quot; rel=&quot;nofollow&quot;&gt;http://rowan.wordpress.com/files/2009/07/kevo.gif&lt;/a&gt;

Only lasted on the site for about an hour before we had to remove it due to lack of sense of humour. :-)]]></description>
		<content:encoded><![CDATA[<p>Via Twitter <a href="http://twitter.com/ajobbins" rel="nofollow">@ajobbins</a> reminded me of this excellent example of Fire &amp; motion:</p>
<p><a href="http://rowan.wordpress.com/files/2009/07/kevo.gif" rel="nofollow">http://rowan.wordpress.com/files/2009/07/kevo.gif</a></p>
<p>Only lasted on the site for about an hour before we had to remove it due to lack of sense of humour. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowan Simpson</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10437</link>
		<dc:creator><![CDATA[Rowan Simpson]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 03:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10437</guid>
		<description><![CDATA[

&lt;blockquote&gt;Animated ad&#039;s effectiveness is inversely proportional to our ability to ignore them. Unfortunately their irritating-ness is proportional to their effectiveness... &lt;/blockquote&gt;



Is that true?  It seems so on the surface, but I&#039;d be interested to   see some numbers. 

PS what are these &quot;DVDs&quot; you talk of? ;-) 

]]></description>
		<content:encoded><![CDATA[<blockquote><p>Animated ad&#8217;s effectiveness is inversely proportional to our ability to ignore them. Unfortunately their irritating-ness is proportional to their effectiveness&#8230; </p></blockquote>
<p>Is that true?  It seems so on the surface, but I&#8217;d be interested to   see some numbers. </p>
<p>PS what are these &#8220;DVDs&#8221; you talk of? ;-) </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Reid</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10435</link>
		<dc:creator><![CDATA[Luke Reid]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 21:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10435</guid>
		<description><![CDATA[RE: Animated ads

When these started I installed an ad-blocking plugin to firefox. Now I use a different browser, and although I haven&#039;t installed a new plugin - I don&#039;t need to. 

Over 90% of the time I spend on the same sites which I essentially boycott if they have animated ads. I.e. I read BBC news rather than stuff. 

Unfortunately Trademe has a monopoly in NZ (I think - will now do further research).

Animated ad&#039;s effectiveness is inversely proportional to our ability to ignore them. Unfortunately their irritating-ness is proportional to their effectiveness...

I think it comes down to a simple call - is our site essential enough that we can piss off our users and they will still come back. In the case of trademe, with a near monopoly - the answer is certainly yes. 
 
Site owners should love their users and thank them for making the site a reality by visiting it, rather than overly trying to monetise them _at users expense_

Rant over - that feels better, animated ad&#039;s bug me as much as that anti-piracy techno video at the start of DVDs these days]]></description>
		<content:encoded><![CDATA[<p>RE: Animated ads</p>
<p>When these started I installed an ad-blocking plugin to firefox. Now I use a different browser, and although I haven&#8217;t installed a new plugin &#8211; I don&#8217;t need to. </p>
<p>Over 90% of the time I spend on the same sites which I essentially boycott if they have animated ads. I.e. I read BBC news rather than stuff. </p>
<p>Unfortunately Trademe has a monopoly in NZ (I think &#8211; will now do further research).</p>
<p>Animated ad&#8217;s effectiveness is inversely proportional to our ability to ignore them. Unfortunately their irritating-ness is proportional to their effectiveness&#8230;</p>
<p>I think it comes down to a simple call &#8211; is our site essential enough that we can piss off our users and they will still come back. In the case of trademe, with a near monopoly &#8211; the answer is certainly yes. </p>
<p>Site owners should love their users and thank them for making the site a reality by visiting it, rather than overly trying to monetise them _at users expense_</p>
<p>Rant over &#8211; that feels better, animated ad&#8217;s bug me as much as that anti-piracy techno video at the start of DVDs these days</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10434</link>
		<dc:creator><![CDATA[alex]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 17:41:01 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10434</guid>
		<description><![CDATA[I feel the new design if very clinical feeling, a little bit of colour in the  right places could have made a world of difference.

One thing i don&#039;t feel was good, was the transition, they changed the site so much, that when I logged in the following day, I thought I was on the wrong site, and went and clicked on my bookmark again.

It can&#039;t be a great idea to alienate your user audience like that.

I also use kiwibank which has had a new redesign and for a week or two before the transition they showed an image of what it will look like when they change, and it was an easy transition and felt comfortable when it happened. Obviously a bank is a last place you want people to feel insecure about being on the wrong site.

kiwibank has also gone with a fixed width design, but they have retained some elements that go full width, and overall I am really impressed with the design and usability enhancements they have come up with]]></description>
		<content:encoded><![CDATA[<p>I feel the new design if very clinical feeling, a little bit of colour in the  right places could have made a world of difference.</p>
<p>One thing i don&#8217;t feel was good, was the transition, they changed the site so much, that when I logged in the following day, I thought I was on the wrong site, and went and clicked on my bookmark again.</p>
<p>It can&#8217;t be a great idea to alienate your user audience like that.</p>
<p>I also use kiwibank which has had a new redesign and for a week or two before the transition they showed an image of what it will look like when they change, and it was an easy transition and felt comfortable when it happened. Obviously a bank is a last place you want people to feel insecure about being on the wrong site.</p>
<p>kiwibank has also gone with a fixed width design, but they have retained some elements that go full width, and overall I am really impressed with the design and usability enhancements they have come up with</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Haylock</title>
		<link>http://rowansimpson.com/2009/07/12/whats-in-it-for-me/#comment-10433</link>
		<dc:creator><![CDATA[Mark Haylock]]></dc:creator>
		<pubDate>Sun, 12 Jul 2009 12:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://rowansimpson.com/?p=2013#comment-10433</guid>
		<description><![CDATA[I can&#039;t say that my first impression of the changes was very positive. I wouldn&#039;t say that they&#039;ve grown on me either, I&#039;ve become numb to them more than anything else.

For me personally I think that emotion is an important part of any design (talking here about both graphic and UX design). A great design produces a tailored positive emotional response in the user and a bad design produces either no emotion or (worse) a negative emotional response. These emotions contribute to both the users first impressions and their overall experience.

When your switching from an existing design like TradeMe has then you also have to deal with the emotion that existing users feel for the old design and their reaction to loosing it. When a significant portion of your revenue comes from those existing users then your really should respect that and offer real value to those users along with any change you make. As you say, the benefits appear to be mostly to TradeMe themselves and not their users.

Ignoring the fact that their was a previous design, my immediate response to the new design is that it&#039;s not particularly attractive, it lacks character and is a little rough around the edges. That and annoying things like the fixed width design plus the obnoxious ads means that I&#039;m not emotionally engaged in a positive way. Of course that&#039;s my subjective opinion.

Is it just me or does the new header design seem to have the same influences as the stuff.co.nz redesign?

I&#039;m a big fan of good semantic HTML, but it looks like TradeMe has caught a case of divitis and classitis... which imho is as bad as being a tableholic ;)]]></description>
		<content:encoded><![CDATA[<p>I can&#8217;t say that my first impression of the changes was very positive. I wouldn&#8217;t say that they&#8217;ve grown on me either, I&#8217;ve become numb to them more than anything else.</p>
<p>For me personally I think that emotion is an important part of any design (talking here about both graphic and UX design). A great design produces a tailored positive emotional response in the user and a bad design produces either no emotion or (worse) a negative emotional response. These emotions contribute to both the users first impressions and their overall experience.</p>
<p>When your switching from an existing design like TradeMe has then you also have to deal with the emotion that existing users feel for the old design and their reaction to loosing it. When a significant portion of your revenue comes from those existing users then your really should respect that and offer real value to those users along with any change you make. As you say, the benefits appear to be mostly to TradeMe themselves and not their users.</p>
<p>Ignoring the fact that their was a previous design, my immediate response to the new design is that it&#8217;s not particularly attractive, it lacks character and is a little rough around the edges. That and annoying things like the fixed width design plus the obnoxious ads means that I&#8217;m not emotionally engaged in a positive way. Of course that&#8217;s my subjective opinion.</p>
<p>Is it just me or does the new header design seem to have the same influences as the stuff.co.nz redesign?</p>
<p>I&#8217;m a big fan of good semantic HTML, but it looks like TradeMe has caught a case of divitis and classitis&#8230; which imho is as bad as being a tableholic ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

