One of the most frequently asked questions in my Web usability course is "What screen resolution should we design for?" The full answer is a bit tricky, but the basic advice is clear:
Optimize for 1024×768, which is currently the most widely used screen size. Of course, the general guideline is to optimize for your target audience's most common resolution, so the size will change in the future. It might even be a different size now, if, say, you're designing an intranet for a company that gives all employees big monitors.
Do not design solely for a specific monitor size because screen sizes vary among users. Window size variability is even greater, since users don't always maximize their browsers (especially if they have large screens).
Use a liquid layout that stretches to the current user's window size (that is, avoid frozen layouts that are always the same size).
Currently, about 60% of all monitors are set at 1024×768 pixels. (See historical trends and newer data for screen sizes.) In comparison, only about 17% use 800×600 so it's obviously less important to aim at perfection for these small-display users. What's equally obvious, however, is that you can't simply ignore 17% of your customer segment by providing a frozen layout that requires more screen space than they have available.
Optimizing for 1024×768
When I say "optimize" I mean that your page should look and work the best at the most common size. It should still look good and work well at other sizes, which is why I recommend a liquid layout. But it should be its best at 1024×768.
The three main criteria in optimizing a page layout for a certain screen size are:
Initial visibility: Is all key information visible above the fold so users can see it without scrolling? This is a tradeoff between how many items are shown vs. how much detail is displayed for each item.
Readability: How easy is it to read the text in various columns, given their allocated width?
Aesthetics: How good does your page look when the elements are at the proper size and location for this screen size? Do all the elements line up correctly — that is, are captions immediately next to the photos, etc.?
You should also consider all three criteria at the full range of sizes, continuously resizing the browser window from 800×600 to 1280×1024. Your page should score high on all criteria throughout the entire resolution range.
Your page should also work at even smaller and bigger sizes, though such extremes are less important. Fewer than half a percent of users still have 640×480. Although such users should certainly be able to access your site, giving them a less-than-great design is an acceptable compromise.
As the first criterion implies, scrolling is always a key consideration. Users generally don't like to scroll (see newer data on the distribution of users' attention above vs. below the fold). So, when you design, you should consider how much users can see if they scroll only a screenfull or two.
Both scrolling and initial visibility obviously depend on screen size: Bigger screens show more content above the fold and require less scrolling. This is where you have to optimize for 1024×768: present your most compelling material above the fold at this resolution (while ensuring that the absolutely critical information remains visible at 800×600).
So, what about tiny screens, such as those found on mobile devices? A liquid design should scale all the way down to a phone, but don't assume that this is how you should deliver your company's mobile user experience. Mobile environments are special; to optimize for them, you must design a separate service that provides fewer features, is written even more concisely, and is more context aware.
Many users have large displays. Currently, about 18% of users have at least 1280×1024. The percentage of users with big screens is growing, though not as fast as I would like.
Big monitors are the easiest way to increase white-collar productivity, and anyone who makes at least $50,000 per year ought to have at least 1600×1200 screen resolution. A flat-panel display with this resolution currently costs less than $500. So, as long as the bigger display increases productivity by at least 0.5%, you'll recover the investment in less than a year. (The typical corporate overhead doubles the company's per-employee cost; always remember to use loaded cost, not take-home salary, in any productivity calculation.)
Apple and Microsoft have both published reports that attempt to quantify the productivity gains from bigger monitors. Sadly, the studies don't provide credible numbers because of various methodological weaknesses. My experience shows estimated productivity gains of 5–10% when users do knowledge work on a big monitor. This translates into about an 0.5–1% increase in overall productivity for a person who does screen-focused knowledge work 10% of the day. There's no doubt that big screens are worth the money.
I personally use a 2048×1536 display, and I wouldn't even call that a really big screen. Within the next 10 years, I expect monitors of, say, 5000×3000 to be in fairly common use, at least among high-end business professionals.
Starting at 1600×1200, users rarely stretch their browser windows to the full screen because few websites work well on such a wide canvas. Big windows are magic for working on spreadsheets, graphic design, and many other tasks, but not for the current paradigm of Web pages. Today, big-screen Web users typically utilize their extra space for multiple windows and parallel browsing.
To serve Web users with truly big screens in the future, we'll probably need a different paradigm than individual pages. Perhaps a more newspaper-like metaphor or a different information dashboard will prove superior down the road.
In any case, the need for a new paradigm in the future doesn't change current recommendations: optimize for 1024×768, but don't design solely for this size. Your pages should work at any resolution, from 800×600 to 1280×1024 and beyond.
(See also: newer article about page design for bigger monitors than those discussed here.)
Share :Twitter | LinkedIn | Google+ | Email