<?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: Are You Designing for the Smaller Screen?</title>
	<atom:link href="http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/feed" rel="self" type="application/rss+xml" />
	<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen</link>
	<description>Design, Develop, and Grow</description>
	<lastBuildDate>Sun, 21 Mar 2010 19:46:27 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Metropolis</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175806</link>
		<dc:creator>Metropolis</dc:creator>
		<pubDate>Sun, 07 Sep 2008 23:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175806</guid>
		<description>[...] de Identidad Corporativa en PDF - 9 Top CSS Essential Skills&#8230; - Rags, widows &amp; orphans - Are you designing for the small screen? - How to be a good client - Cómo ser un diseñador independiente y no perecer en el intento - [...]</description>
		<content:encoded><![CDATA[<p>[...] de Identidad Corporativa en PDF &#8211; 9 Top CSS Essential Skills&#8230; &#8211; Rags, widows &amp; orphans &#8211; Are you designing for the small screen? &#8211; How to be a good client &#8211; Cómo ser un diseñador independiente y no perecer en el intento &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Babbs</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175652</link>
		<dc:creator>Matthew Babbs</dc:creator>
		<pubDate>Tue, 02 Sep 2008 12:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175652</guid>
		<description>I guess clean XHTML doesn&#039;t include paragraph tags. Sorry about that!</description>
		<content:encoded><![CDATA[<p>I guess clean XHTML doesn&#8217;t include paragraph tags. Sorry about that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Babbs</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175651</link>
		<dc:creator>Matthew Babbs</dc:creator>
		<pubDate>Tue, 02 Sep 2008 12:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175651</guid>
		<description>I&#039;m not a fan of the idea that there should be a separate &#039;mobile web&#039;&#8212;rather, I see it as just &#039;the web&#039;, accessed by many different devices in many different places. So I don&#039;t serve an entire separate mobile-optimised site, but I do cater to low resolutions in two ways.One, I make sure the basic design scales well down to at least 800x480, as that&#039;s the minimum resolution likely to be found going forwards. (Scaling down to 640x480 is good, but people using a screen that small are probably also using a browser so old that it doesn&#039;t get my CSS.)Two, I serve an @media handheld stylesheet. Most people who seriously browse with phones or other ultra-mobile devices will be using a browser (like Opera Mini/Mobile or Safari Mobile, and in the future Android and Fennec) that accepts this. As I&#039;d be serving the same content if I had a separate site at mobi.example.com, I can handle all the necessary changes to layout, text size and so on in CSS. I can even point to lightweight, scaled-down background images if necessary, although generally I just turn these off.In the future, I&#039;ll be able to optimise this approach further, by using CSS3 @media screen resolution queries.There is a problem with this approach: content images. It&#039;s not as big a problem for me as it might be, because my style tends to the minimalist, but I know that sooner or later I&#039;m going to land a client who likes oversized images. Using the browser to resize images or doing server-side resolution sniffing are poor solutions, and having a separate site for mobiles won&#039;t help netbook users. Are there other solutions out there?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a fan of the idea that there should be a separate &#8216;mobile web&#8217;&mdash;rather, I see it as just &#8216;the web&#8217;, accessed by many different devices in many different places. So I don&#8217;t serve an entire separate mobile-optimised site, but I do cater to low resolutions in two ways.One, I make sure the basic design scales well down to at least 800&#215;480, as that&#8217;s the minimum resolution likely to be found going forwards. (Scaling down to 640&#215;480 is good, but people using a screen that small are probably also using a browser so old that it doesn&#8217;t get my CSS.)Two, I serve an @media handheld stylesheet. Most people who seriously browse with phones or other ultra-mobile devices will be using a browser (like Opera Mini/Mobile or Safari Mobile, and in the future Android and Fennec) that accepts this. As I&#8217;d be serving the same content if I had a separate site at mobi.example.com, I can handle all the necessary changes to layout, text size and so on in CSS. I can even point to lightweight, scaled-down background images if necessary, although generally I just turn these off.In the future, I&#8217;ll be able to optimise this approach further, by using CSS3 @media screen resolution queries.There is a problem with this approach: content images. It&#8217;s not as big a problem for me as it might be, because my style tends to the minimalist, but I know that sooner or later I&#8217;m going to land a client who likes oversized images. Using the browser to resize images or doing server-side resolution sniffing are poor solutions, and having a separate site for mobiles won&#8217;t help netbook users. Are there other solutions out there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175196</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 18 Aug 2008 16:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175196</guid>
		<description>jardel you can redirect people to another page depending on there screen resolution. This can easily be mastered with javascript.

How to: http://www.pageresource.com/jscript/jscreen.htm</description>
		<content:encoded><![CDATA[<p>jardel you can redirect people to another page depending on there screen resolution. This can easily be mastered with javascript.</p>
<p>How to: <a href="http://www.pageresource.com/jscript/jscreen.htm" rel="nofollow">http://www.pageresource.com/jscript/jscreen.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thord Daniel Hedengren</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175192</link>
		<dc:creator>Thord Daniel Hedengren</dc:creator>
		<pubDate>Mon, 18 Aug 2008 09:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175192</guid>
		<description>Thanks for your input, all.

@jardel,
That&#039;s right, there are GUI stuff to take into consideration as well.</description>
		<content:encoded><![CDATA[<p>Thanks for your input, all.</p>
<p>@jardel,<br />
That&#8217;s right, there are GUI stuff to take into consideration as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jardel</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175184</link>
		<dc:creator>jardel</dc:creator>
		<pubDate>Sun, 17 Aug 2008 01:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175184</guid>
		<description>You forget one thing! There are the browser area where tabs and address bars stays, the start menu of OS, the status bar of browser, this all takes space on the screen too!

i like to support 800x600 or more, not less. As a owner of a site with 3 sidebars developing for brazil, 800x600 is pretty common (actually, the second after 1024~) and ie6 is common too! But i&#039;m not going to do re-designs for little screens, i&#039;ve been using thumb sizes in a fixed &quot;max 380 width&quot; for long, if people in these laptop screens start to search old posts - what is inevitable, as most of us design our sites do engage readership -  they will have to scroll horizontally! 

I would like to remove one sidebar or even both for the &quot;little screen&quot; people, but i don&#039;t have the skill and it will kill all the usability i&#039;ve planned for months, i don&#039;t know if there is a way to show one site for one screen size and another site for another screen size, but i think this will be the best choice</description>
		<content:encoded><![CDATA[<p>You forget one thing! There are the browser area where tabs and address bars stays, the start menu of OS, the status bar of browser, this all takes space on the screen too!</p>
<p>i like to support 800&#215;600 or more, not less. As a owner of a site with 3 sidebars developing for brazil, 800&#215;600 is pretty common (actually, the second after 1024~) and ie6 is common too! But i&#8217;m not going to do re-designs for little screens, i&#8217;ve been using thumb sizes in a fixed &#8220;max 380 width&#8221; for long, if people in these laptop screens start to search old posts &#8211; what is inevitable, as most of us design our sites do engage readership &#8211;  they will have to scroll horizontally! </p>
<p>I would like to remove one sidebar or even both for the &#8220;little screen&#8221; people, but i don&#8217;t have the skill and it will kill all the usability i&#8217;ve planned for months, i don&#8217;t know if there is a way to show one site for one screen size and another site for another screen size, but i think this will be the best choice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175179</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 16 Aug 2008 19:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175179</guid>
		<description>Its something to think about but hard to design for with the very small screens in mind as it could cause problems of too much white space on a normal or large resolution screen.</description>
		<content:encoded><![CDATA[<p>Its something to think about but hard to design for with the very small screens in mind as it could cause problems of too much white space on a normal or large resolution screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best of the Week by Abduzeedo &#171; Guiwells&#8217;s Blog</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175178</link>
		<dc:creator>Best of the Week by Abduzeedo &#171; Guiwells&#8217;s Blog</dc:creator>
		<pubDate>Sat, 16 Aug 2008 17:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175178</guid>
		<description>[...] Are You Designing for the Smaller Screen? [...]</description>
		<content:encoded><![CDATA[<p>[...] Are You Designing for the Smaller Screen? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Angelo Racoma</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175171</link>
		<dc:creator>J. Angelo Racoma</dc:creator>
		<pubDate>Sat, 16 Aug 2008 11:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175171</guid>
		<description>When I created my Eee-oriented site &lt;a href=&quot;http://www.myasuseee.com&quot; rel=&quot;nofollow&quot;&gt;myasuseee.com&lt;/a&gt;, I looked for a free WP theme that was plain and uncluttered, and that would look nice on a 840px width screen.

These days, though, wider netbook screens are becoming more popular, with many already sporting 1024x600 screens, like my EeePC 900 and many others, including the MSI Wind, most EeePC models, and the Acer Aspire one. That means less horizontal scrolling!

My HP Mini Note even has a 1280x768 screen, which is the same resolution as my bigger laptop (but this is a rarity).</description>
		<content:encoded><![CDATA[<p>When I created my Eee-oriented site <a href="http://www.myasuseee.com" rel="nofollow">myasuseee.com</a>, I looked for a free WP theme that was plain and uncluttered, and that would look nice on a 840px width screen.</p>
<p>These days, though, wider netbook screens are becoming more popular, with many already sporting 1024&#215;600 screens, like my EeePC 900 and many others, including the MSI Wind, most EeePC models, and the Acer Aspire one. That means less horizontal scrolling!</p>
<p>My HP Mini Note even has a 1280&#215;768 screen, which is the same resolution as my bigger laptop (but this is a rarity).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Freelance Friday: My Writing Week 33 &#124; tdhedengren</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175168</link>
		<dc:creator>Freelance Friday: My Writing Week 33 &#124; tdhedengren</dc:creator>
		<pubDate>Fri, 15 Aug 2008 18:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175168</guid>
		<description>[...] Are You Designing for the Smaller Screen?Talking about designing for smaller screens on Devlounge [...]</description>
		<content:encoded><![CDATA[<p>[...] Are You Designing for the Smaller Screen?Talking about designing for smaller screens on Devlounge [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.devlounge.net/design/are-you-designing-for-the-smaller-screen/comment-page-1#comment-175154</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Thu, 14 Aug 2008 20:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/?p=1638#comment-175154</guid>
		<description>It&#039;s always a good thing to try to keep in your head while designing. These mobile screens are starting to pop up everywhere.

- &lt;a href=&quot;http://submitcss.com&quot; rel=&quot;nofollow&quot;&gt;Greg&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>It&#8217;s always a good thing to try to keep in your head while designing. These mobile screens are starting to pop up everywhere.</p>
<p>- <a href="http://submitcss.com" rel="nofollow">Greg</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
