<?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: Formatting my blog for the iPhone</title>
	<atom:link href="http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/</link>
	<description>Improving the human experience one day at a time</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:53:46 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: iPhone Aholic</title>
		<link>http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/comment-page-1/#comment-3284</link>
		<dc:creator>iPhone Aholic</dc:creator>
		<pubDate>Wed, 18 Mar 2009 06:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-3284</guid>
		<description>The blog looks great on the iphone now!</description>
		<content:encoded><![CDATA[<p>The blog looks great on the iphone now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whitney</title>
		<link>http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/comment-page-1/#comment-135</link>
		<dc:creator>whitney</dc:creator>
		<pubDate>Sat, 01 Mar 2008 23:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-135</guid>
		<description>&lt;a class=&quot;comment_link&quot; href=&quot;http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-131&quot; rel=&quot;nofollow&quot;&gt;Dan&lt;/a&gt;, I completely agree. When it comes to readability, performance and recognizability, it&#039;s in your best interest to ensure that your blog/website/content of any kind can be accessed on any browser, particularly one as popular as Safari for the iPhone.

If it works without any special love, all the better. If not, do what it takes to make it work.

As you and &lt;a class=&quot;comment_link&quot; href=&quot;http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-132&quot; rel=&quot;nofollow&quot;&gt;Eduardo&lt;/a&gt; both pointed out, the best solution would be to tweak the iPhone theme so that it closely matches my current theme. Perhaps I&#039;ll take a crack at it some rainy, lonely day in the future. For now, I&#039;m sticking with Cutline.</description>
		<content:encoded><![CDATA[<p><a class="comment_link" href="http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-131" rel="nofollow">Dan</a>, I completely agree. When it comes to readability, performance and recognizability, it&#8217;s in your best interest to ensure that your blog/website/content of any kind can be accessed on any browser, particularly one as popular as Safari for the iPhone.</p>
<p>If it works without any special love, all the better. If not, do what it takes to make it work.</p>
<p>As you and <a class="comment_link" href="http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-132" rel="nofollow">Eduardo</a> both pointed out, the best solution would be to tweak the iPhone theme so that it closely matches my current theme. Perhaps I&#8217;ll take a crack at it some rainy, lonely day in the future. For now, I&#8217;m sticking with Cutline.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eduardo</title>
		<link>http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/comment-page-1/#comment-132</link>
		<dc:creator>Eduardo</dc:creator>
		<pubDate>Sat, 01 Mar 2008 23:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-132</guid>
		<description>Definitely the one made for the iPhone, since I don&#039;t have to turn my phone to read your entries. It reads natural (to me).

There must be a way to tweak it to match your current blog-theme, no?</description>
		<content:encoded><![CDATA[<p>Definitely the one made for the iPhone, since I don&#8217;t have to turn my phone to read your entries. It reads natural (to me).</p>
<p>There must be a way to tweak it to match your current blog-theme, no?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://whitneyhess.com/blog/2008/03/01/formatting-my-blog-for-the-iphone/comment-page-1/#comment-131</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sat, 01 Mar 2008 23:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://whitneyhess.com/blog/2008/03/formatting-my-blog-for-the-iphone/#comment-131</guid>
		<description>(Happy to help.)

So, I&#039;m of two minds about the whole formatted-for-iPhone thing.

In some cases, especially when you&#039;re trying to quickly communicate data (headlines, weather, tweets, etc.), there&#039;s really no question: an iPhone-optimized interface is best. (Compare the &lt;a href=&quot;http://www.wunderground.com/&quot; rel=&quot;nofollow&quot;&gt;Weather Underground&lt;/a&gt; with its svelte &lt;a href=&quot;http://i.wund.com&quot; rel=&quot;nofollow&quot;&gt;iPhone version&lt;/a&gt;.)

For a blog, I don&#039;t think it&#039;s that straightforward. Especially when your site&#039;s design is a huge part of what makes it distinctive, you might be better off letting the iPhone do its best with the real thing.  Of course, if your blog starts out unreadable (I&#039;m looking at you, MySpace), it&#039;s only going to get worse on the iPhone, but a decently-designed blog fares pretty well at QVGA, 160 ppi. 

As far as whitneyhess.com goes, Cutline feels pretty similar to the NYT web design, and Apple uses the Times as a marquee piece for Mobile Safari, so I think you&#039;re pretty safe without a custom iPhone version.

However, I think if you took that iPhone WordPress plugin and really made it your own, that might be the best of both worlds.  (That&#039;s what I tried to do with my friend&#039;s &lt;a href=&quot;http://sportsgirlblog.com&quot; rel=&quot;nofollow&quot;&gt;sports blog&lt;/a&gt;; the &lt;a href=&quot;http://dsandler.org/entries/images/2008/sportsgirl-iphone.jpg&quot; rel=&quot;nofollow&quot;&gt;iPhone version&lt;/a&gt; feels very similar, but without extraneous navigation and decoration.  Streamlined, but visually of the same family.)</description>
		<content:encoded><![CDATA[<p>(Happy to help.)</p>
<p>So, I&#8217;m of two minds about the whole formatted-for-iPhone thing.</p>
<p>In some cases, especially when you&#8217;re trying to quickly communicate data (headlines, weather, tweets, etc.), there&#8217;s really no question: an iPhone-optimized interface is best. (Compare the <a href="http://www.wunderground.com/" rel="nofollow">Weather Underground</a> with its svelte <a href="http://i.wund.com" rel="nofollow">iPhone version</a>.)</p>
<p>For a blog, I don&#8217;t think it&#8217;s that straightforward. Especially when your site&#8217;s design is a huge part of what makes it distinctive, you might be better off letting the iPhone do its best with the real thing.  Of course, if your blog starts out unreadable (I&#8217;m looking at you, MySpace), it&#8217;s only going to get worse on the iPhone, but a decently-designed blog fares pretty well at QVGA, 160 ppi. </p>
<p>As far as whitneyhess.com goes, Cutline feels pretty similar to the NYT web design, and Apple uses the Times as a marquee piece for Mobile Safari, so I think you&#8217;re pretty safe without a custom iPhone version.</p>
<p>However, I think if you took that iPhone WordPress plugin and really made it your own, that might be the best of both worlds.  (That&#8217;s what I tried to do with my friend&#8217;s <a href="http://sportsgirlblog.com" rel="nofollow">sports blog</a>; the <a href="http://dsandler.org/entries/images/2008/sportsgirl-iphone.jpg" rel="nofollow">iPhone version</a> feels very similar, but without extraneous navigation and decoration.  Streamlined, but visually of the same family.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.561 seconds -->
