<?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: iPhone-specific pages are a bad idea</title>
	<atom:link href="http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/</link>
	<description>A blog on entrepreneurship, user experience, and web innovation. Published by Fred Oliveira.</description>
	<lastBuildDate>Tue, 13 Dec 2011 18:19:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: New Media Signal - Today&#8217;s Top Blog Posts on New Media - Powered by SocialRank</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41201</link>
		<dc:creator>New Media Signal - Today&#8217;s Top Blog Posts on New Media - Powered by SocialRank</dc:creator>
		<pubDate>Mon, 01 Oct 2007 10:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41201</guid>
		<description>[...] Webreakstuff &#187; iPhone-specific pages are a bad idea [...]</description>
		<content:encoded><![CDATA[<p>[...] Webreakstuff &raquo; iPhone-specific pages are a bad idea [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ash Haque</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41197</link>
		<dc:creator>Ash Haque</dc:creator>
		<pubDate>Sat, 22 Sep 2007 23:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41197</guid>
		<description>$399 now :-)</description>
		<content:encoded><![CDATA[<p>$399 now :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcdave.net &#187; links for 2007-09-15</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41193</link>
		<dc:creator>mcdave.net &#187; links for 2007-09-15</dc:creator>
		<pubDate>Sat, 15 Sep 2007 06:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41193</guid>
		<description>[...] Webreakstuff Ã‚Â» iPhone-specific pages are a bad idea Design for the experience, not the device (tags: iphone design web) [...]</description>
		<content:encoded><![CDATA[<p>[...] Webreakstuff Ã‚Â» iPhone-specific pages are a bad idea Design for the experience, not the device (tags: iphone design web) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenan Banks</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41185</link>
		<dc:creator>Kenan Banks</dc:creator>
		<pubDate>Fri, 07 Sep 2007 19:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41185</guid>
		<description>Just a note:  Steve Jobs visited the iPhone-specific Facebook site during his speech announcing the new iPods.  

That alone was probably worth the development effort...</description>
		<content:encoded><![CDATA[<p>Just a note:  Steve Jobs visited the iPhone-specific Facebook site during his speech announcing the new iPods.  </p>
<p>That alone was probably worth the development effort&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clark</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41183</link>
		<dc:creator>Clark</dc:creator>
		<pubDate>Fri, 07 Sep 2007 00:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41183</guid>
		<description>Actually I think the apps and sites specifically designed for the iPhone, like Facebook and Dig, end up being far more usable, thereby providing a far better experience than the sites or apps that spawned them.  They are uncluttered by advertising, task focused, and not over-designed like so many sites today.</description>
		<content:encoded><![CDATA[<p>Actually I think the apps and sites specifically designed for the iPhone, like Facebook and Dig, end up being far more usable, thereby providing a far better experience than the sites or apps that spawned them.  They are uncluttered by advertising, task focused, and not over-designed like so many sites today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevin</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41182</link>
		<dc:creator>kevin</dc:creator>
		<pubDate>Wed, 05 Sep 2007 19:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41182</guid>
		<description>Interesting points all around. Most of them however are very technical in nature and ignore whether or not it is smart marketing. In some cases an iPhone specific site could be the entirely wrong idea and a waste of resources. However, if your target audience embraces the Apple brand association, has a large enough population of iPhone users and the iPhone supports interface functionality that would improve the usability of application, then there may be a case for one. I wouldn&#039;t dismiss the entire idea at all.</description>
		<content:encoded><![CDATA[<p>Interesting points all around. Most of them however are very technical in nature and ignore whether or not it is smart marketing. In some cases an iPhone specific site could be the entirely wrong idea and a waste of resources. However, if your target audience embraces the Apple brand association, has a large enough population of iPhone users and the iPhone supports interface functionality that would improve the usability of application, then there may be a case for one. I wouldn&#8217;t dismiss the entire idea at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenan Banks</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41181</link>
		<dc:creator>Kenan Banks</dc:creator>
		<pubDate>Wed, 05 Sep 2007 01:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41181</guid>
		<description>To me, it&#039;s no dumber than worrying about Safari compatibility.  To the &quot;pragmatic&quot; programmer, it&#039;s a ridiculous waste of time to spend much time at all for 2% of your users, especially when you know they may well ALSO have Firefox.  

But a lot of people worry about Safari anyway. Why?  Well there are two reasons

First reason is that you&#039;re a gigantic company like Google, and you expect XX million people to hit your app, and discounting XXX hundred thousand is unacceptable.  

Second reason is that you trade somewhat on your app&#039;s &quot;coolness&quot;, and Safari users are disproportionately cool and vocal.  Safari users are more likely to try you out and talk about you if you&#039;re cool.  

Now replace &quot;Safari&quot; with &quot;iPhone&quot;.  

There&#039;s pretty much nothing you can buy today that gets you more geek cred than the iPhone. Designing an iPhone-specific page makes you kinda cool by corollary.  

Yes I have an iPhone.  And I admit to visiting iphone.facebook.com fairly regularly.</description>
		<content:encoded><![CDATA[<p>To me, it&#8217;s no dumber than worrying about Safari compatibility.  To the &#8220;pragmatic&#8221; programmer, it&#8217;s a ridiculous waste of time to spend much time at all for 2% of your users, especially when you know they may well ALSO have Firefox.  </p>
<p>But a lot of people worry about Safari anyway. Why?  Well there are two reasons</p>
<p>First reason is that you&#8217;re a gigantic company like Google, and you expect XX million people to hit your app, and discounting XXX hundred thousand is unacceptable.  </p>
<p>Second reason is that you trade somewhat on your app&#8217;s &#8220;coolness&#8221;, and Safari users are disproportionately cool and vocal.  Safari users are more likely to try you out and talk about you if you&#8217;re cool.  </p>
<p>Now replace &#8220;Safari&#8221; with &#8220;iPhone&#8221;.  </p>
<p>There&#8217;s pretty much nothing you can buy today that gets you more geek cred than the iPhone. Designing an iPhone-specific page makes you kinda cool by corollary.  </p>
<p>Yes I have an iPhone.  And I admit to visiting iphone.facebook.com fairly regularly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AndrÃƒÂ©</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41176</link>
		<dc:creator>AndrÃƒÂ©</dc:creator>
		<pubDate>Fri, 31 Aug 2007 09:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41176</guid>
		<description>Allan, I&#039;m sorry to disappoint you but switching css sheets aren&#039;t going to make the experience excellent... specially since that solution will force the browser to download the markup anyways. And on handheld devices, even on wifi, that can kill the experience right from the start.

Anyway, I agree with Fred. Designing for a specific device was, is and will ever be dumb. Specially on such a diverse market as the mobile browsers. Those webapps that came out all in one week (facebook, netvibes) were indeed enchanced for the iPhone, although, they worked fairly well on other handheld devices. I tested those on my Nokia 6630 with Opera Mini and I can tell you it wasn&#039;t as pleasant as using it on the iPhone (i guess) but it worked. So, kudos to them.

I guess this is nothing more than a fad, or a marketing move. Making an iPhone version of your website sounds cooler to the average joe than making a mobile version, doesn&#039;t it? (to me it doesn&#039;t, but that&#039;s besides the point)

Make your mobile webapps work on a variety of phones. And please, please, if you _HAVE_ to go with javascript at least use it unobtrusively... mobile scripting support is very very scarce at the moment. So if you&#039;re going to do it, do it right and don&#039;t alienate the majority of the market.</description>
		<content:encoded><![CDATA[<p>Allan, I&#8217;m sorry to disappoint you but switching css sheets aren&#8217;t going to make the experience excellent&#8230; specially since that solution will force the browser to download the markup anyways. And on handheld devices, even on wifi, that can kill the experience right from the start.</p>
<p>Anyway, I agree with Fred. Designing for a specific device was, is and will ever be dumb. Specially on such a diverse market as the mobile browsers. Those webapps that came out all in one week (facebook, netvibes) were indeed enchanced for the iPhone, although, they worked fairly well on other handheld devices. I tested those on my Nokia 6630 with Opera Mini and I can tell you it wasn&#8217;t as pleasant as using it on the iPhone (i guess) but it worked. So, kudos to them.</p>
<p>I guess this is nothing more than a fad, or a marketing move. Making an iPhone version of your website sounds cooler to the average joe than making a mobile version, doesn&#8217;t it? (to me it doesn&#8217;t, but that&#8217;s besides the point)</p>
<p>Make your mobile webapps work on a variety of phones. And please, please, if you _HAVE_ to go with javascript at least use it unobtrusively&#8230; mobile scripting support is very very scarce at the moment. So if you&#8217;re going to do it, do it right and don&#8217;t alienate the majority of the market.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allan branch</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41175</link>
		<dc:creator>allan branch</dc:creator>
		<pubDate>Thu, 30 Aug 2007 13:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41175</guid>
		<description>Mobile business expense tracking for http://www.LessAccounting.com will be optimized for the iphone.  Its just a faster to load/minimal view of the normal page.  We use the same html just flip css sheets.</description>
		<content:encoded><![CDATA[<p>Mobile business expense tracking for <a href="http://www.LessAccounting.com" rel="nofollow">http://www.LessAccounting.com</a> will be optimized for the iphone.  Its just a faster to load/minimal view of the normal page.  We use the same html just flip css sheets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Omli</title>
		<link>http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/comment-page-1/#comment-41172</link>
		<dc:creator>Hans Omli</dc:creator>
		<pubDate>Tue, 28 Aug 2007 19:48:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.webreakstuff.com/2007/08/iphone-specific-pages-are-a-bad-idea/#comment-41172</guid>
		<description>I couldn&#039;t agree more that &quot;designing pages exclusively for the iPhone is a dumb idea&quot;.  However, I&#039;m not sure iPhone fits in the category of &quot;mobile devices in general&quot; though.

iPhone is a display-centric device that uses touch as the interaction model.  On the other hand, a Blackberry is arguably more input-centric whereas a &quot;basic&quot; cell phone is essentially a cordless phone with (relatively) limited display or input ability.

While impractical to design specifically for each and every device, as product designers we have responsibility to offer experiences acceptable to the different interaction models of our users.  Just as a video game designer may incorporate motion deeply into a Wii version of a video game, a web designer can incorporate touch deeply into an interface that is appropriate for both the iPhone and other &quot;touch&quot; devices where qwerty input is less optimal (e.g. Opera on the Wii).</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more that &#8220;designing pages exclusively for the iPhone is a dumb idea&#8221;.  However, I&#8217;m not sure iPhone fits in the category of &#8220;mobile devices in general&#8221; though.</p>
<p>iPhone is a display-centric device that uses touch as the interaction model.  On the other hand, a Blackberry is arguably more input-centric whereas a &#8220;basic&#8221; cell phone is essentially a cordless phone with (relatively) limited display or input ability.</p>
<p>While impractical to design specifically for each and every device, as product designers we have responsibility to offer experiences acceptable to the different interaction models of our users.  Just as a video game designer may incorporate motion deeply into a Wii version of a video game, a web designer can incorporate touch deeply into an interface that is appropriate for both the iPhone and other &#8220;touch&#8221; devices where qwerty input is less optimal (e.g. Opera on the Wii).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

