<?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: Designing for 800&#215;600?</title>
	<atom:link href="http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/feed/" rel="self" type="application/rss+xml" />
	<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/</link>
	<description>My meandering thoughts about Oracle, Application Express and life in general</description>
	<lastBuildDate>Mon, 05 Sep 2011 05:48:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Sam Hall</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-462188</link>
		<dc:creator>Sam Hall</dc:creator>
		<pubDate>Tue, 10 Nov 2009 06:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-462188</guid>
		<description>For a technology blog, I&#039;d aim for smart phone friendly templates (mine took me about 2 hours to set up and reads well now in all resolutions).

For applications, well that&#039;s up to you and your clients to negotiate. I personally always go for 1024x768 as a minimum these days. 800x600 hasn&#039;t been demanded of me for years now. More and more requests for smart phone support keep coming my way recently though.

As you&#039;re no doubt well aware, the standard APEX templates are a nightmare for web designers, this is the real issue. A good template should render nicely in any resolution.

If I had the time I&#039;d make an iPhone friendly template for APEX. For now, I generally just ask what functionality is most useful to have access to from a phone and duplicate a very small subset of the features of the system on a few iPhone specific pages.</description>
		<content:encoded><![CDATA[<p>For a technology blog, I&#8217;d aim for smart phone friendly templates (mine took me about 2 hours to set up and reads well now in all resolutions).</p>
<p>For applications, well that&#8217;s up to you and your clients to negotiate. I personally always go for 1024&#215;768 as a minimum these days. 800&#215;600 hasn&#8217;t been demanded of me for years now. More and more requests for smart phone support keep coming my way recently though.</p>
<p>As you&#8217;re no doubt well aware, the standard APEX templates are a nightmare for web designers, this is the real issue. A good template should render nicely in any resolution.</p>
<p>If I had the time I&#8217;d make an iPhone friendly template for APEX. For now, I generally just ask what functionality is most useful to have access to from a phone and duplicate a very small subset of the features of the system on a few iPhone specific pages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Scott</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-461895</link>
		<dc:creator>John Scott</dc:creator>
		<pubDate>Fri, 06 Nov 2009 18:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-461895</guid>
		<description>Just to clarify...I&#039;m not saying that you should make sites that don&#039;t work in 800x600. I was trying to say that you should not design your site to &#039;look best&#039; at 800x600 or use 800x600 as your baseline.

John.</description>
		<content:encoded><![CDATA[<p>Just to clarify&#8230;I&#8217;m not saying that you should make sites that don&#8217;t work in 800&#215;600. I was trying to say that you should not design your site to &#8216;look best&#8217; at 800&#215;600 or use 800&#215;600 as your baseline.</p>
<p>John.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall Litchfield</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-461864</link>
		<dc:creator>Niall Litchfield</dc:creator>
		<pubDate>Fri, 06 Nov 2009 13:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-461864</guid>
		<description>The logic still likely applies to Amazon, but it&#039;s 3.5% not 5% as per http://marketshare.hitslink.com/report.aspx?qprid=17 which is a leading source of market share information and certainly not developer related. Fuel for the fire though, 1680x1050 is a higher share of the audience and I bet the folk asking for 800x600 view it as a niche.</description>
		<content:encoded><![CDATA[<p>The logic still likely applies to Amazon, but it&#8217;s 3.5% not 5% as per <a href="http://marketshare.hitslink.com/report.aspx?qprid=17" rel="nofollow">http://marketshare.hitslink.com/report.aspx?qprid=17</a> which is a leading source of market share information and certainly not developer related. Fuel for the fire though, 1680&#215;1050 is a higher share of the audience and I bet the folk asking for 800&#215;600 view it as a niche.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Scott</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-461863</link>
		<dc:creator>John Scott</dc:creator>
		<pubDate>Fri, 06 Nov 2009 13:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-461863</guid>
		<description>Hi Paulo,

Sure, that&#039;s why I included the line -

&quot;Now there are a few cases where this definitely is a real requirement&quot;.

John.</description>
		<content:encoded><![CDATA[<p>Hi Paulo,</p>
<p>Sure, that&#8217;s why I included the line -</p>
<p>&#8220;Now there are a few cases where this definitely is a real requirement&#8221;.</p>
<p>John.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Hall</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-461843</link>
		<dc:creator>Tim Hall</dc:creator>
		<pubDate>Fri, 06 Nov 2009 11:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-461843</guid>
		<description>Hi.

I agree. It very much depends on your business and target.

If you are Amazon, losing 5% of the market represents a massive loss, so you decision process will be different than someone building for their company intranet.

I know lots of people that still build IE only sites because they know they have a captive audience. :)

I think we should make web pages that fail if you are on anything but the latest browser. :)

Cheers

Tim...</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>I agree. It very much depends on your business and target.</p>
<p>If you are Amazon, losing 5% of the market represents a massive loss, so you decision process will be different than someone building for their company intranet.</p>
<p>I know lots of people that still build IE only sites because they know they have a captive audience. :)</p>
<p>I think we should make web pages that fail if you are on anything but the latest browser. :)</p>
<p>Cheers</p>
<p>Tim&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paulo Vale</title>
		<link>http://jes.blogs.shellprompt.net/2009/11/06/designing-for-800x600/comment-page-1/#comment-461834</link>
		<dc:creator>Paulo Vale</dc:creator>
		<pubDate>Fri, 06 Nov 2009 10:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://jes.blogs.shellprompt.net/?p=280#comment-461834</guid>
		<description>Hi John,

You must not forget the audience type. Your blog is almost for sure visited mainly by developers, that supposedly have better hardware resources than the rest of the population.

I guess it all depends on the target of the application you&#039;re developing. I give you an example. We have at Neoface an Internet ERP solution that is supposed to work with small POS screens.

But if we are talking about traditional web applications/websites, you&#039;re absolutely right... a bigger war is to get rid of ie6 :)</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>You must not forget the audience type. Your blog is almost for sure visited mainly by developers, that supposedly have better hardware resources than the rest of the population.</p>
<p>I guess it all depends on the target of the application you&#8217;re developing. I give you an example. We have at Neoface an Internet ERP solution that is supposed to work with small POS screens.</p>
<p>But if we are talking about traditional web applications/websites, you&#8217;re absolutely right&#8230; a bigger war is to get rid of ie6 :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

