<?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: Fennec &#8211; Mobile Optimzed Web Pages</title>
	<atom:link href="http://starkravingfinkle.org/blog/2009/11/fennec-mobile-optimzed-web-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://starkravingfinkle.org/blog/2009/11/fennec-mobile-optimzed-web-pages/</link>
	<description></description>
	<lastBuildDate>Fri, 23 Dec 2011 21:18:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Colby Russell</title>
		<link>http://starkravingfinkle.org/blog/2009/11/fennec-mobile-optimzed-web-pages/comment-page-1/#comment-9526</link>
		<dc:creator>Colby Russell</dc:creator>
		<pubDate>Thu, 12 Nov 2009 22:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=594#comment-9526</guid>
		<description>Duda Mobile, I&#039;m not sure if that comment was a response to what I wrote, but in any case I&#039;ve replied here as well as to the post you linked to on your blog.

If accessing your &quot;normal&quot; website on a mobile device is painful, &lt;em&gt;your &quot;normal&quot; website sucks&lt;/em&gt;. The solution is not to divide your time into making a mobile-targeted website and a desktop-targeted website, it&#039;s to make an accessible website from the start. You&#039;ll end up with happy mobile users, the (potentially silent) subset of users who found your website frustrating to access on the desktop will shrink, and it will be available to both parties in a fraction of the time that it would if you were to develop two separate websites; there will be no down period for mobile users while you&#039;re trying to put something together.</description>
		<content:encoded><![CDATA[<p>Duda Mobile, I&#8217;m not sure if that comment was a response to what I wrote, but in any case I&#8217;ve replied here as well as to the post you linked to on your blog.</p>
<p>If accessing your &#8220;normal&#8221; website on a mobile device is painful, <em>your &#8220;normal&#8221; website sucks</em>. The solution is not to divide your time into making a mobile-targeted website and a desktop-targeted website, it&#8217;s to make an accessible website from the start. You&#8217;ll end up with happy mobile users, the (potentially silent) subset of users who found your website frustrating to access on the desktop will shrink, and it will be available to both parties in a fraction of the time that it would if you were to develop two separate websites; there will be no down period for mobile users while you&#8217;re trying to put something together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duda Mobile</title>
		<link>http://starkravingfinkle.org/blog/2009/11/fennec-mobile-optimzed-web-pages/comment-page-1/#comment-9524</link>
		<dc:creator>Duda Mobile</dc:creator>
		<pubDate>Thu, 12 Nov 2009 08:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=594#comment-9524</guid>
		<description>Thanks for keeping us posted on what&#039;s coming down the line from FF. For your readers who are wondering why they would need a mobile optimized website I invite them to read this post: http://blog.dudamobile.com/why-build-a-mobile-website/</description>
		<content:encoded><![CDATA[<p>Thanks for keeping us posted on what&#8217;s coming down the line from FF. For your readers who are wondering why they would need a mobile optimized website I invite them to read this post: <a href="http://blog.dudamobile.com/why-build-a-mobile-website/" rel="nofollow">http://blog.dudamobile.com/why-build-a-mobile-website/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colby Russell</title>
		<link>http://starkravingfinkle.org/blog/2009/11/fennec-mobile-optimzed-web-pages/comment-page-1/#comment-9516</link>
		<dc:creator>Colby Russell</dc:creator>
		<pubDate>Tue, 10 Nov 2009 07:33:47 +0000</pubDate>
		<guid isPermaLink="false">http://starkravingfinkle.org/blog/?p=594#comment-9516</guid>
		<description>I thought the whole point behind Fennec was for mobile web users to experience the web as-it-is, and not some marginal, crippled, mobile version? Doesn&#039;t implementing hooks for the web on mobile devices encourage the bad habit of creating discrete versions?

Rather than taking these kinds of counterproductive steps, shouldn&#039;t we instead be telling people to &lt;em&gt;always&lt;/em&gt; design pages to scale, with no guarantee for viewport size? Not only does it prevent the marginalization issue that results from the &quot;I&#039;ll get around to it sometime&quot; parallel development process, but just because I am viewing on a widescreen display doesn&#039;t mean that I want my browser to require that I dedicate the full dimensions of my screen to it. With increasingly larger screens, my productivity should &lt;em&gt;increase&lt;/em&gt;. When you consider that studies find that reading efficiency decreases when the widths of columns of text approach the size of today&#039;s typical displays, you realize that exactly the opposite is occurring: people are less productive when they&#039;re reading Wikipedia through a maximized window on a 20 inch, 1600 pixel display than they would have been if they were reading from a maximized window on a supposedly inferior display from last decade.</description>
		<content:encoded><![CDATA[<p>I thought the whole point behind Fennec was for mobile web users to experience the web as-it-is, and not some marginal, crippled, mobile version? Doesn&#8217;t implementing hooks for the web on mobile devices encourage the bad habit of creating discrete versions?</p>
<p>Rather than taking these kinds of counterproductive steps, shouldn&#8217;t we instead be telling people to <em>always</em> design pages to scale, with no guarantee for viewport size? Not only does it prevent the marginalization issue that results from the &#8220;I&#8217;ll get around to it sometime&#8221; parallel development process, but just because I am viewing on a widescreen display doesn&#8217;t mean that I want my browser to require that I dedicate the full dimensions of my screen to it. With increasingly larger screens, my productivity should <em>increase</em>. When you consider that studies find that reading efficiency decreases when the widths of columns of text approach the size of today&#8217;s typical displays, you realize that exactly the opposite is occurring: people are less productive when they&#8217;re reading Wikipedia through a maximized window on a 20 inch, 1600 pixel display than they would have been if they were reading from a maximized window on a supposedly inferior display from last decade.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

