<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: How to make your web content look stunning on the iPhone 4&#8242;s new Retina display</title>
	<atom:link href="http://aralbalkan.com/3331/feed" rel="self" type="application/rss+xml" />
	<link>http://aralbalkan.com/3331</link>
	<description>Passionate geekisms.</description>
	<lastBuildDate>Sun, 12 Feb 2012 17:52:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Patrick H. Lauke</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-264920</link>
		<dc:creator>Patrick H. Lauke</dc:creator>
		<pubDate>Sun, 18 Dec 2011 13:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-264920</guid>
		<description>Sorry, late to the game here, but I was just testing some browser behaviour relating to this and stumbled across your post. My question: for web content, why bother with the specific media query stuff to serve higher-dpi images only to high-dpi devices? Why not just specify the high-dpi versions in all cases, and let browsers on lower-dpi devices render the graphic down? Is it purely to have absolute pixel-perfect control over how things look on low-dpi devices? And not just with CSS, also good old image elements...</description>
		<content:encoded><![CDATA[<p>Sorry, late to the game here, but I was just testing some browser behaviour relating to this and stumbled across your post. My question: for web content, why bother with the specific media query stuff to serve higher-dpi images only to high-dpi devices? Why not just specify the high-dpi versions in all cases, and let browsers on lower-dpi devices render the graphic down? Is it purely to have absolute pixel-perfect control over how things look on low-dpi devices? And not just with CSS, also good old image elements&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-264771</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Fri, 09 Dec 2011 19:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-264771</guid>
		<description>thanks! This helped me out greatly</description>
		<content:encoded><![CDATA[<p>thanks! This helped me out greatly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Probert</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-263726</link>
		<dc:creator>Lee Probert</dc:creator>
		<pubDate>Thu, 25 Aug 2011 14:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-263726</guid>
		<description>Would make sense for the time being for Safari on an iPhone 4 to do the image swap in exactly the same way it would for the native apps.

Until there&#039;s a slicker solution that works with all &#039;future&#039; hi-res displays.</description>
		<content:encoded><![CDATA[<p>Would make sense for the time being for Safari on an iPhone 4 to do the image swap in exactly the same way it would for the native apps.</p>
<p>Until there&#8217;s a slicker solution that works with all &#8216;future&#8217; hi-res displays.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: datenkind</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-263153</link>
		<dc:creator>datenkind</dc:creator>
		<pubDate>Thu, 14 Jul 2011 14:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-263153</guid>
		<description>Thanks for this little guide. I just stumbled over some problems with a small embedded webserver that fracked up the SVG i used for menu icons and which worked great on the Retina – when not using this embedded server. I can’t re-engineer the problem, but I just did it your ways – and it just works. :)</description>
		<content:encoded><![CDATA[<p>Thanks for this little guide. I just stumbled over some problems with a small embedded webserver that fracked up the SVG i used for menu icons and which worked great on the Retina – when not using this embedded server. I can’t re-engineer the problem, but I just did it your ways – and it just works. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Designing for the Retina Display (326ppi) &#171; bento blogging</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-262627</link>
		<dc:creator>Designing for the Retina Display (326ppi) &#171; bento blogging</dc:creator>
		<pubDate>Fri, 27 May 2011 02:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-262627</guid>
		<description>[...] How to make your web content look stunning on the iPhone 4’s new Retina display by Aral Balkan outlines the high-level impact of the Retina Display on Web design &amp; development. [...]</description>
		<content:encoded><![CDATA[<p>[...] How to make your web content look stunning on the iPhone 4’s new Retina display by Aral Balkan outlines the high-level impact of the Retina Display on Web design &amp; development. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy matthews</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-261994</link>
		<dc:creator>andy matthews</dc:creator>
		<pubDate>Tue, 11 Jan 2011 20:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-261994</guid>
		<description>Thanks for this article Aral. Exactly what I needed for the mobile website I&#039;m building.</description>
		<content:encoded><![CDATA[<p>Thanks for this article Aral. Exactly what I needed for the mobile website I&#8217;m building.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max C</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-261805</link>
		<dc:creator>Max C</dc:creator>
		<pubDate>Mon, 29 Nov 2010 12:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-261805</guid>
		<description>It isn&#039;t the start of resolution independence, it&#039;s the end!  Once displays hit 300dpi, there is no further to go.  That&#039;s the resolution magazines are produced at.  Once 300dpi is commonplace, it will be the standard resolution forever.</description>
		<content:encoded><![CDATA[<p>It isn&#8217;t the start of resolution independence, it&#8217;s the end!  Once displays hit 300dpi, there is no further to go.  That&#8217;s the resolution magazines are produced at.  Once 300dpi is commonplace, it will be the standard resolution forever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy Mcilvena</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-261619</link>
		<dc:creator>Troy Mcilvena</dc:creator>
		<pubDate>Mon, 25 Oct 2010 21:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-261619</guid>
		<description>For the jQuery users:

http://troymcilvena.com/post/998277515/jquery-retina

For MooTools users:

http://mootools.net/forge/p/mooretina</description>
		<content:encoded><![CDATA[<p>For the jQuery users:</p>
<p><a href="http://troymcilvena.com/post/998277515/jquery-retina" rel="nofollow">http://troymcilvena.com/post/998277515/jquery-retina</a></p>
<p>For MooTools users:</p>
<p><a href="http://mootools.net/forge/p/mooretina" rel="nofollow">http://mootools.net/forge/p/mooretina</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Alexander</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-261602</link>
		<dc:creator>Anthony Alexander</dc:creator>
		<pubDate>Fri, 22 Oct 2010 06:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-261602</guid>
		<description>Once again mac fans have no clue what they are talking about. It&#039;s troubling.</description>
		<content:encoded><![CDATA[<p>Once again mac fans have no clue what they are talking about. It&#8217;s troubling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://aralbalkan.com/3331/comment-page-1#comment-261578</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 18 Oct 2010 10:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://aralbalkan.com/?p=3331#comment-261578</guid>
		<description>An important advice: It&#039;s better to use the Webkit-specific CSS property &quot;-webkit-background-size&quot; instead of the generel &quot;background-size&quot; because iOS 3.1 can&#039;t interpret the latter.</description>
		<content:encoded><![CDATA[<p>An important advice: It&#8217;s better to use the Webkit-specific CSS property &#8220;-webkit-background-size&#8221; instead of the generel &#8220;background-size&#8221; because iOS 3.1 can&#8217;t interpret the latter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

