<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Brain Sparks Browser Stats</title>
	<atom:link href="http://www.uie.com/brainsparks/2005/10/26/brain-sparks-browser-stats/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2005/10/26/brain-sparks-browser-stats/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 11 Feb 2012 08:11:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Dave Feldman</title>
		<link>http://www.uie.com/brainsparks/2005/10/26/brain-sparks-browser-stats/comment-page-1/#comment-199</link>
		<dc:creator>Dave Feldman</dc:creator>
		<pubDate>Fri, 28 Oct 2005 11:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=95#comment-199</guid>
		<description>...And in case market share isn&#039;t sufficient reason, I like to point out to my clients that Firefox is easier to do initial development and debugging on. Its JavaScript Console, DOM Inspector, and excellent Web Developer extension are terrific for tracking down CSS and JavaScript issues, while IE&#039;s JavaScript error window is cryptic at best. Plus it makes a better demo/mockup platform due to its better standards support and near-identical rendering across platforms.</description>
		<content:encoded><![CDATA[<p>&#8230;And in case market share isn&#8217;t sufficient reason, I like to point out to my clients that Firefox is easier to do initial development and debugging on. Its JavaScript Console, DOM Inspector, and excellent Web Developer extension are terrific for tracking down CSS and JavaScript issues, while IE&#8217;s JavaScript error window is cryptic at best. Plus it makes a better demo/mockup platform due to its better standards support and near-identical rendering across platforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Parker Smith</title>
		<link>http://www.uie.com/brainsparks/2005/10/26/brain-sparks-browser-stats/comment-page-1/#comment-191</link>
		<dc:creator>Parker Smith</dc:creator>
		<pubDate>Wed, 26 Oct 2005 17:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=95#comment-191</guid>
		<description>I think that Eric&#039;s last paragraph is very important to note. You just can&#039;t design to exclusion. But for me, I think understanding other site metrics is an important consideration in understanding your own site&#039;s success.

If you didn&#039;t know that Google had 90% IE users - you could happily go about coding Site X and assume 60% FF use on it was standard and no big deal. But knowing that Google reports 90% IE traffic tells you that Site X&#039;s 60% FF score is &quot;special&quot; for one reason or another. 

Perhaps Site X has found a niche (good thing). Perhaps IE doesn&#039;t render the page correctly, driving customers away (bad thing).  Does the 60% FF use mean that Site X is missing a sales or revenue opportunity with all those IE users that aren&#039;t coming back? Do people who use IE represent a market segment that hasn&#039;t been tapped? 

I feel like these are all important questions - particularly for eCommerce sites. But without a valid reference set, you don&#039;t really have anything to compare to. Therefore you don&#039;t have a good understanding of where your site strengths and growth opportunities are.</description>
		<content:encoded><![CDATA[<p>I think that Eric&#8217;s last paragraph is very important to note. You just can&#8217;t design to exclusion. But for me, I think understanding other site metrics is an important consideration in understanding your own site&#8217;s success.</p>
<p>If you didn&#8217;t know that Google had 90% IE users &#8211; you could happily go about coding Site X and assume 60% FF use on it was standard and no big deal. But knowing that Google reports 90% IE traffic tells you that Site X&#8217;s 60% FF score is &#8220;special&#8221; for one reason or another. </p>
<p>Perhaps Site X has found a niche (good thing). Perhaps IE doesn&#8217;t render the page correctly, driving customers away (bad thing).  Does the 60% FF use mean that Site X is missing a sales or revenue opportunity with all those IE users that aren&#8217;t coming back? Do people who use IE represent a market segment that hasn&#8217;t been tapped? </p>
<p>I feel like these are all important questions &#8211; particularly for eCommerce sites. But without a valid reference set, you don&#8217;t really have anything to compare to. Therefore you don&#8217;t have a good understanding of where your site strengths and growth opportunities are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://www.uie.com/brainsparks/2005/10/26/brain-sparks-browser-stats/comment-page-1/#comment-189</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Wed, 26 Oct 2005 15:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=95#comment-189</guid>
		<description>This is why I say-- and, in fact, said during one of my talks at UI10-- that &quot;industry yardstick&quot; figures are worse than useless, they&#039;re misleading.  What matters is who&#039;s visiting your site (or sites), not who&#039;s visiting Google or Yahoo! or the sites Chuck uses to gather his statistics.

meyerweb.com shows a similar usage pattern, and that&#039;s perhaps interesting, but it&#039;s of no practical use to someone who has their own site to worry about.  If 95% of your users are on Netscape 4.x, well then you have to worry about how the site works in Netscape 4.x.  If your site gets 90% IE/Win users, then IE/Win isn&#039;t something you can ignore.  For Brian Sparks and my site, Firefox is the &quot;baseline&quot; browser; the one that has to be considered first, because it&#039;s the majority.

(Note I didn&#039;t say &quot;considered to the exclusion of all others&quot;.  I wouldn&#039;t expect you to draw that inference, but I have to state it explicitly because every time I bring up this point, somebody accuses me of being unrealistic and advocating dropping support for IE, when I&#039;ve never done any such thing.)

At any rate, interesting to see another site with similar demographics to mine!</description>
		<content:encoded><![CDATA[<p>This is why I say&#8211; and, in fact, said during one of my talks at UI10&#8211; that &#8220;industry yardstick&#8221; figures are worse than useless, they&#8217;re misleading.  What matters is who&#8217;s visiting your site (or sites), not who&#8217;s visiting Google or Yahoo! or the sites Chuck uses to gather his statistics.</p>
<p>meyerweb.com shows a similar usage pattern, and that&#8217;s perhaps interesting, but it&#8217;s of no practical use to someone who has their own site to worry about.  If 95% of your users are on Netscape 4.x, well then you have to worry about how the site works in Netscape 4.x.  If your site gets 90% IE/Win users, then IE/Win isn&#8217;t something you can ignore.  For Brian Sparks and my site, Firefox is the &#8220;baseline&#8221; browser; the one that has to be considered first, because it&#8217;s the majority.</p>
<p>(Note I didn&#8217;t say &#8220;considered to the exclusion of all others&#8221;.  I wouldn&#8217;t expect you to draw that inference, but I have to state it explicitly because every time I bring up this point, somebody accuses me of being unrealistic and advocating dropping support for IE, when I&#8217;ve never done any such thing.)</p>
<p>At any rate, interesting to see another site with similar demographics to mine!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

