Designing for 800×600?

I’ve lost count of the number of times I’ve heard people say “The site must be designed to work in 800×600 resolution”. Now there are a few cases where this definitely is a real requirement, however often it’s more of a case that people don’t want to potentially exclude people from their site (and if it’s a commercial site why wouldn’t you want to appeal to the widest possible audience?).

However, how many people really use an 800×600 resolution these days? Out of interest I took a look at the statistics from my blog (the one you’re reading right now) for yesterday (I posted a new post yesterday so it would be interesting to see the stats for the new views just for yesterday rather than over the entire lifetime of the site).

Browser Resolutions

So, whilst I’m not trying to pretend that these figures are representative of any other sites out there. They highlight a couple of things to me.

1) Nobody visited my site using 800×600 resolution.

2) The smallest resolution was 320×396 (probably an iPhone or other mobile device). After that the next smallest was 1024×768.

3) There are quite a lot of variations in browser resolution, more than I expected really.

So, what’s my point here? Well…I don’t really have one….other than –

1) Needing to support 800×600 is very different to designing the site in 800×600. In other words it’s no bad thing to have your site gracefully degrade to working nicely in 800×600, but I certainly wouldn’t make the starting design 800×600, otherwise you’d spending effort where there seems to be least reward.

2) 1024×768 is now becoming over-shadowed by higher resolutions. Most laptops these days support higher resolutions than that, let alone desktops. Most developers I know have multiple monitors too.

So, don’t be afraid of challenging the requirement of “We must design for 800×600″…how many people are *really* using it? Let’s stamp it out now…

6 thoughts on “Designing for 800×600?

  1. Paulo Vale

    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’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’re absolutely right… a bigger war is to get rid of ie6 🙂


  2. Tim Hall


    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. 🙂




  3. John Scott

    Hi Paulo,

    Sure, that’s why I included the line –

    “Now there are a few cases where this definitely is a real requirement”.



  4. John Scott

    Just to clarify…I’m not saying that you should make sites that don’t work in 800×600. I was trying to say that you should not design your site to ‘look best’ at 800×600 or use 800×600 as your baseline.



  5. Sam Hall

    For a technology blog, I’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’s up to you and your clients to negotiate. I personally always go for 1024×768 as a minimum these days. 800×600 hasn’t been demanded of me for years now. More and more requests for smart phone support keep coming my way recently though.

    As you’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’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.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s