<?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: Approaches to Mobile Web Development Part 2 &#8211; Separate Sites</title>
	<atom:link href="http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/</link>
	<description>For make benefit of glorious tubes</description>
	<lastBuildDate>Mon, 17 Jun 2013 17:13:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jason Grlicky</title>
		<link>http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/comment-page-1/#comment-216389</link>
		<dc:creator>Jason Grlicky</dc:creator>
		<pubDate>Mon, 23 May 2011 20:21:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/webdev/?p=1710#comment-216389</guid>
		<description><![CDATA[Samat: If I&#039;m not mistaken, I think both AMO and SUMO are using the django-mobility library to house their shared detection logic:

https://github.com/jbalogh/django-mobility

Hope that helps!]]></description>
		<content:encoded><![CDATA[<p>Samat: If I&#8217;m not mistaken, I think both AMO and SUMO are using the django-mobility library to house their shared detection logic:</p>
<p><a href="https://github.com/jbalogh/django-mobility" rel="nofollow">https://github.com/jbalogh/django-mobility</a></p>
<p>Hope that helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samat</title>
		<link>http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/comment-page-1/#comment-216352</link>
		<dc:creator>Samat</dc:creator>
		<pubDate>Thu, 19 May 2011 05:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/webdev/?p=1710#comment-216352</guid>
		<description><![CDATA[Could someone list where in the AMO and SUMO codebases user agent detection is performed?]]></description>
		<content:encoded><![CDATA[<p>Could someone list where in the AMO and SUMO codebases user agent detection is performed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: groovecoder</title>
		<link>http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/comment-page-1/#comment-216331</link>
		<dc:creator>groovecoder</dc:creator>
		<pubDate>Wed, 18 May 2011 02:59:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/webdev/?p=1710#comment-216331</guid>
		<description><![CDATA[love these posts. inspiring for what we&#039;ll do with developer.mozilla.org]]></description>
		<content:encoded><![CDATA[<p>love these posts. inspiring for what we&#8217;ll do with developer.mozilla.org</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Fink</title>
		<link>http://blog.mozilla.org/webdev/2011/05/13/approaches-to-mobile-web-development-part-2-separate-sites/comment-page-1/#comment-216054</link>
		<dc:creator>Steve Fink</dc:creator>
		<pubDate>Fri, 13 May 2011 19:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/webdev/?p=1710#comment-216054</guid>
		<description><![CDATA[It seems worth mentioning that another drawback of this approach is that a web site&#039;s idea of what works on a mobile device is often very different from the actual users&#039;, to the point that many mobile users prefer to use the desktop version. It&#039;s a big hammer, and it&#039;s very easy to get lazy and smash some fingers with it.

Sometimes it&#039;s a matter of the site author guessing wrong (or not tailoring properly to what makes mobile different); sometimes it&#039;s different motivations (eg it may be easier to get to the content and avoid ads on the desktop version.)]]></description>
		<content:encoded><![CDATA[<p>It seems worth mentioning that another drawback of this approach is that a web site&#8217;s idea of what works on a mobile device is often very different from the actual users&#8217;, to the point that many mobile users prefer to use the desktop version. It&#8217;s a big hammer, and it&#8217;s very easy to get lazy and smash some fingers with it.</p>
<p>Sometimes it&#8217;s a matter of the site author guessing wrong (or not tailoring properly to what makes mobile different); sometimes it&#8217;s different motivations (eg it may be easier to get to the content and avoid ads on the desktop version.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
