Skip to page content or skip to Accesskey List.
Search evolt.org
evolt.org login: or register

Work

Main Page Content

640 x 480 Isn't Dead Just Yet

Rated 4.34 (Ratings: 20) (Add your rating)

Log in to add a comment
(49 comments so far)

Want more?

 
Picture of aardvark

Adrian Roselli

Member info | Full bio

User since: December 13, 1998

Last login: July 07, 2010

Articles written: 79

I've always kept a little list going of reasons why I still design for monitors and windows set to 640x480, and a list of reasons why I don't want to design for 640x480 anymore. My reasons for accommodating 640x480 users are still rock-steady in my mind, while the reasons against still don't cut it.

Compiled below is my list of reasons, with caveats, that I maintain for reference whenever I find that client who wants to design only for his or her monitor, forgetting about the wide variety of users out there. I should also qualify this by stating that the real problem with designing outside of the 640x480 box isn't really the 480 height, since most users are accustomed to scrolling down, but the width. Many people never notice the scrollbar on the bottom and those that do resent having to scroll left to right to left to right, etc, just to read your content or navigate your site.

Readability

If you need to use more than 600 pixels for a line of text, you need to be aware of readability issues. Keeping lines of text around 30-70 characters offers the best readability for the widest variety of users. This holds true on the web as well as in print, where hundreds of years of printed text has taught professionals that very same lesson. Go beyond that, and readability begins to suffer.

Now, obviously many users may have their fonts set to varying sizes, but usually these different sizes still cause the viewable text to fall into the broad range of 30-70 characters. Avoid the opposite — setting the fonts of your site to painfully small at 640x480 to get all your information onscreen at 640x480. This is about quality, not quantity. If you tailor your design so the smallest fonts a user will reasonably select get 70 characters per line, and the largest fonts they might select get 30 characters per line, you are right on target. And don't worry about throwing an occasional image into your content (resulting in, say, rows of 20 character-per-line copy), because that design element helps break up the content for the reader, giving their eye somewhere to rest. Keep in mind the reading styles of people on the web, and their desire to get to information quickly. Unless this broad swath of text is the actual content for which a user has searched, there is probably too much text.

Some readers may be familiar with Jakob Nielson and his Alertbox articles. Some readers may think he is full of it (after all, it's not like his own site is a poster boy for usability), but the articles cited below have been referenced time and again and have withstood more than 2 years of challenges. I think these three articles cover the usability issues I've pointed out above rather nicely in case you should want more detail.

Images

If you are scaling your images up to take advantage of all the space available in a larger-than-640x480 window, your images are most likely too large. Similar images of much smaller sizes, for smaller resolutions, are much smaller in file size as well. Larger images may be too much for a user to download, and may lead to serious congestion and problems displaying other images on the page.

Another interesting, though somewhat out-of-date with regard to future technology trends, Jakob Nielson article is The Need for Speed (March 1, 1997). It covers some of the issues you need to consider when you ask a user to download anything, including any and every page on your site. While not always true, generally when people are given more space in which to design, they will fill it up, abandoning white space, filling the area with imagery and copy. Restricting that space can help you create smaller and faster pages, resulting in a better user experience. If it is a special case, like detailed product specifications, give the user a thumbnail view, with the option to download a larger file of specified file size. Also, consider other data formats besides just imagery, such as pull quotes.

Printing

If your site is an information repository, or even if it is frequented by only a select group of customers, many people have a tendency to print pages out. Just look around your office at the stacks of articles printed from CNN. Whenever possible, people will print out the information to read in a more comfortable and natural fashion. Remember, how you use the site may not be the same way other people use it, so be careful assuming that since you don't need to print it, no one else would either.

A 600px site still fits rather nicely on an 8.5" sheet of paper in portrait. Consider a 72 pixels-per-inch monitor with a 640 pixel wide browser window full of text and images, with say 50 pixels allotted to white space, scrollbars, and window frames. When you do the math, you can see that 590 pixels at 72ppi comes out to 8.2 inches, assuring that the printout and the web site may be identical. Anything larger results in scaling or cropping of your pages, something you may not wish to have happen if it breaks your site identity or causes tables or images to span pages. This also means that, if your site is designed for it, you don't need to offer separate printable pages, which require a set of separate templates, database calls, or even a series of hard-coded HTML files.

Design

There are some basic statements I will make that, while they aren't fact by their very nature, they are still valid points, and ones I give out to clients and co-workers. You shouldn't need all that space. If you need a larger canvas just to fit your white space, then your design is too big. If you need a larger canvas just to show your content, your content is too big and you may need to scale it down. The information overload alone could render the site unusable without some spectacular interface design. Keep in mind people's attention spans on the web are short.

Compatibility

Some folks just don't know that the factory default of 640x480 can be switched, a default that still exists on many computers today, especially low-end business computers. At least you can ensure that those users can still use your site, that you haven't alienated any of them, or confused them by hiding content or navigation off the side of the page. While many users are starting to come online with palmtop computers, set-top boxes, and even surfing cell phones, you can be ready when the technology for those devices finally brings them in to the 640x480 world as well, which with current trends, may not be that far off.

Statistics

You've made it this far, now here's some data to back up my arguments. Let's take the 10th GVU WWW User Survey from October 1998 (the most recent one as of this writing). This is a sampling of web users and, in this specific case, their monitor resolutions. The numbers are as follow:

<640x480 11.6%
800x600: 30.7%
1024x768: 27.7%
1152x900: 4.2%
1280X1024: 8.7%
Other: 3.0%
Don't Know:  14.0%

At what resolution shall we assume the Don't Know crowd is running? Let's apply the overall percentages for all other categories to the Don't Know crowd, giving us at least another 1% of users at 640x480. That means that 1 out of very 9 users is running at 640x480 resolution. If we went so far as to assume that the entire Don't Know crowd is running at 640x480, then we would be looking at 1 out of every 4 users at 640x480 resolution.

However, as I said, this is not a truly random sampling. This study is skewed by experienced users, as suggested by the fact that 37% of the respondents claimed to be on the internet for 4-6 years. So let's take a look at users at 640x480 and that don't know based on the number of years of experience they have on the internet, applying the same calculation as above to come up with a rough number:

< 1 Year at 640x480: 17.9% } 24.6%
< 1 Year that don't know: 37.5%
1-3 Years at 640x480: 13.7% } 16.5%
1-3 Years that don't know: 20.3%
> 4 Years at 640x480: 9.6% } 10.3%
> 4 Years that don't know: 7.3%

Now in what category do your users fall? The GVU survey also breaks the statistics down by 'Skill Level,' 'Age Group,' 'Gender,' and 'Location.' If you know your users are all experienced, veteran, male, American users, then perhaps this commentary isn't for you. However, for everyone else, this is a matter of know your audience.

Another place to grab some statistics is at TheCounter.com, a free tracking service for web sites. TheCounter.com gets its data by placing an image on a site, and tracking each browser that requests that image. For the month of June 1999 (Tue Jun 1 00:01:03 1999 - Wed Jun 30 23:59:01 1999), with 321,729,388 visitors, their statistics read like this:

800x600: 53%
1024x768: 22%
640x480: 15%
Unknown: 2%
1152x864: 2%
1280x1024: 2%
1600x1200: 0%

There are many other sources through which you may sift to find information, but these two should have given you a basic idea of what you will discover.

Anecdotal

Who here surfs at full screen anyway?

A founder of evolt.org, Adrian Roselli (aardvark) is the Senior Usability Engineer at Algonquin Studios, located in Buffalo, New York.

Adrian has years of experience in graphic design, web design and multimedia design, as well as extensive experience in internet commerce and interface design and usability. He has been developing for the World Wide Web since its inception, and working the design field since 1993. Adrian is a founding member, board member, and writer to evolt.org. In addition, Adrian sits on the Digital Media Advisory Committee for a local SUNY college and a local private college, as well as the board for a local charter school.

You can see his brand-spanking-new blog at http://blog.adrianroselli.com/ as well as his new web site to promote his writing and speaking at AdrianRoselli.com

Adrian authored the usability case study for evolt.org in Usability: The Site Speaks for Itself, published by glasshaus. He has written three chapters for the book Professional Web Graphics for Non Designers, also published by glasshaus. Adrian also managed to get a couple chapters written (and published) for The Web Professional's Handbook before glasshaus went under. They were really quite good. You should have bought more of the books.

Submitted by Emily on July 19, 1999 - 17:55.

Not me. I'm at 1280x1024 and I find I am irritated when I have to adjust my browser window to accomodate a larger site, particularly if the site is information-oriented. I definitely want to be able to multitask, and having a bunch of windows open that all fill my monitor is not exactly a time saver.

login or register to post comments

Submitted by enenek on August 10, 1999 - 02:50.

i surf always at "site size" - means that i alway shrink browser window to fit the site. of course, sites that need to be full-screen (1280x1024) are always alt+f4 for me.

login or register to post comments

Submitted by pbreit on September 1, 1999 - 17:12.

i hate sites that are larger than 600 or 640 pixels wide. it is rarely necessary to build wider. i have a 21" monitor so it's obviously not that i am not capable of viewing that wide of a page. mac users and more so windows users are not operating applications in "full-screen mode" so maximum screen resolution is less than issue than user preference. ironically, even though pc monitors are getting larger, there are and will continue to be many more new interent devices that have more limited capabilities such as webtv, screen phones and palm pilots (!) so designers with respect for their users will continue to develop more usable sites.

login or register to post comments

Submitted by pcfuel on September 7, 1999 - 08:37.

I think that you can design at 800x600 and still cater to the 640 crowd? Build your pages at 800 and have a column at the right hand edge of the screen that is extra stuff (additional links, related articles, etc?) and have all of your text in a 600 wide region at the left. If you are at 640x480 you won?t realize what you are missing and you can now take advantage of all that extra space. That is what I did on PCFuel.com and it has worked well.

login or register to post comments

Submitted by broFECES on November 10, 1999 - 07:14.

i may the hard-ass here, but i think 640x480 needs to be buried 6 feet under. granted, i try to make fully scalable sites that will work for nearly any size, but that's just something i do to accomodate the medium. i have been tempted to set up a an 'educational' alert box about resolutions when detected, but that's unfortunately not a very savvy thing to do as a web designer. in professional circumstances, i have been told by clients that 640x480 must be 'useable', but target 800x600 and up- which seems to pretty much agree with pcfuel's method. :)

login or register to post comments

Submitted by matrixdc on November 15, 1999 - 16:03.

I have to surf at 800x600 and really hate to scroll horizontally, but I strongly feel that 640x480 is a term of the past and will shortly be in the same place as the terms like 2400 bps. Please excuse me if I seem to harsh.

login or register to post comments

Submitted by marlene on December 8, 1999 - 14:18.

For up to the minute stats on screen resolution, see StatMarket's data.

login or register to post comments

Submitted by miko on December 19, 1999 - 16:10.

I work with hundreds of people who could be considered "web professionals" -- and nearly half use 640x480 resolution on their 20-inch monitors. Why? Because we are all going cross-eyed staring at our screens all day! 640x480 is the setting you use when your eyeballs hurt. Everybody has to get over the idea that 640x480 means old technology, inexperienced user. Granted, there are lots of people with the default setting and they don't even know it, but many people use it by choice. I limit the width of my pages to 585 pixels -- got to remember the browser window takes up a bit of room.

login or register to post comments

Browsing with smaller windows isn't dead yet.

Submitted by leafy on May 23, 2001 - 11:25.

I think that designing for 640x480 is still a matter of (anally-retentive?) personal/professional pride - if you can make your content fit into a reasonably small space and still provide effective navigation, then so much the better. It proves that extra space is not a requirement for effective architecture. However, I have a 19" monitor at work set at 1280x1024, and only surf at full screen when I'm on my lunch and don't want to see the crap behind it - the rest of the time, I keep a small number of relevant windows open (probably not far off 640x480) and stack them for easy access. It annoys me now to be restrained to a site which has been designed for 800x600, and which requires horizontal scrolling if I don't set it to the right size. I wonder if 640x480 really is dead in 2001?

login or register to post comments

640 x 480 easy on the eyes?

Submitted by broFECES on May 23, 2001 - 13:11.

yes, 640 x 480 is easy on the eyes. but i honestly think you have vision issues if you feel the need to use that res all day on 17" or 19" monitor. if it's vision issues, then that's an entirely different thread. leafy posted above that when surfing with multiple instances open, that 640 x 480 is great. i couldn't agree more. i'm fortunate enough that i don't run into that issue since i use 1600 x 1200 for my desktop. granted, i've always had great vision, but i make sure to use quality equipment - the best video card and monitor which suit my needs. and yes, i'm a professional who stares at his screen for 8+ hours every day. i wouldn't say that 640 x 480 is dead though. it's really entirely a matter of specifications. if the people requesting the site design cram so much crap into the screen that it's not realistic, then they need to be informed of this. at this point, the client needs to decide to take the res up a notch, or to rethink the site.

login or register to post comments

Best create a page of 600 pxl width

Submitted by pranab on May 28, 2001 - 04:10.

Although majority of the user uses 800x600 size. It is still worthwhile if you create your whole web page in a center-aligned table of width 600 - if you are not using to much content in your pages and percentage is not let your page look good. When you have real huge content and multiple horizontal tables to use -better use percentage with the target of 800x600.

login or register to post comments

What does Microsoft have to say about it?

Submitted by micah63 on July 11, 2001 - 08:06.

Just a thought - Windows 2000 and Windows 98 are set at 800X600 by default. Another thought - My mom couldn't change the display settings if her life depended on it...

login or register to post comments

800 is the norm

Submitted by urlborg on July 12, 2001 - 10:00.

While it's a great practice to confine text columns to

login or register to post comments

the "game" of scaleability.

Submitted by cursif on August 6, 2001 - 08:19.

as far as im concerned, the whole issue of screen size is one i dont technically pay any attention to. sure, if you check any of my sites, you would see that they all work in pretty much every size.

but i DONT spend any time thinking about that. well... i do notice when a nonbackground image gets wider or longer than i desire on a single screen. but for me, part of the fun and challenge of designing for the web is writing code that scales with the page. the same for the window.

i dont propose any good way to do this, though my own anal retentive methods seem mighty good to me. i just wondered if i was the only person out there actually feeling good about conquering some of the many constraints weve been handed by browser differences, as well as by the aims of markup language on the whole?

login or register to post comments

Reframing the article

Submitted by aardvark on August 6, 2001 - 15:25.

It seems that now, even after the two years this article has been up, people still seem to think it's all about making your pages 580 pixels wide.

That's never what it's said. It's suggested thinking about your users and your design, and determining if you are needlessly cutting some people out, or creating bandwidth-hogging pages, or even capable of tweaking your existing pages to handle everyone.

My usual approach to this problem is to create liquid pages that scale down to sub-600 pixels, and even down to WebTV size in some cases. At that point, the user has control, and I've created a design that can still print, isn't a bandwidth hog, and doesn't look naked at higher resolutions.

When you hardcode, you leave someone out. Don't be that guy/gal/muppet.

login or register to post comments

Fluid design is the way to go.

Submitted by kkuder on August 9, 2001 - 11:35.

I agree with Jeffrey Zeldman and the idea of 'fluid' design, a design that resizes to fit any resolution.

login or register to post comments

640*480 on the net

Submitted by peachpatrol on August 11, 2001 - 10:09.

Most pages designed for 800*600 can easily be viewed with 640, but when it passes 800 it gets pretty boring to scroll when I need to look to the right. I don't mind viewing sites designed for a high resolution as long as they don't put the important stuff to right. So, all you webmasters out there try to put the important stuff to the left and don't make the text lines over 70 characters! Even when I'm using a high resolution it gets hard to read = I leave the site. I'm happy that you people doesn't think that 640 is dead. 'Cause I can't set my resolution any higher. I've designed my webpage to look the same in all resolutions. My website

login or register to post comments

Be ready for every possible resolution

Submitted by Eril on August 14, 2001 - 11:43.

We must remember, that Web now can be accessed not with our 17" or 21" monitors only. There are PDA's, web-tablets and Web-TV. You can't know what resolution exactly your user is browsing with. So, your site have to be ready for every possible one.

login or register to post comments

Vision problems?

Submitted by moonbiter on August 14, 2001 - 14:06.

"yes, 640 x 480 is easy on the eyes. but i honestly think you have vision issues if you feel the need to use that res all day on 17" or 19" monitor. [...] if it's vision issues, then that's an entirely different thread."

That, of course, depends on your definition of "vision issues."

My father, who is in his 50s, had the resolution on his 17-inch monitor set at a resolution of 640 x 480. He told me this is because anything else was uncomfortable for him to read. I recently gave him a 19-inch monitor, at which point 800 x 600 became satisfactory.

His eyes are, by most counts, in average condition for a man of his age.

Although ancedotal, I suspect there is sufficient evidence that my father is not alone in this predicament. This is an important thing to keep in mind when designing sites for use by the general public. A large number of them are not young designers with young eyes.

login or register to post comments

true

Submitted by broFECES on August 14, 2001 - 15:10.

moonbiter - true, but there are many more factors involved with comfortable reading than resolution.

the quality of the monitor, the quality of the video card (this gets much more complex since many good video cards output for text is rather poor), aliased vs anti-alias font smoothing, the lighting in the room (brightness as well as florescent vs incandescent), monitor settings (contrast and brightness), and personal settings for viewing the web.

my father (61 years old) had awful vision (prior to vision surgery). while his vison was bad, i was able to have him comfortably reading online at 1024 on a 17" monitor. he actually thanked me for the clarity as well as the extra real estate.

so i will full acknowldge that for most people, moonbiter, you are probably correct, but being in the IT field, i feel that it is rather easy to provide a comfortable high-resolution for all ages.

login or register to post comments

output for many devices

Submitted by broFECES on August 14, 2001 - 15:13.

oh yes -

output for webTV, handhelds, cell phones, etc.

imo, NOT a reolution issue at the core of the matter. that gets into the realm of data organization and XML, where the content can be output where ever it needs to and it meets the needs of the output. resolution is such a side issue there. and webTV? hahaha. that was made to fail if you ask me. what a pile. it was made first with html2.0 standards if i recall correctly. no thanks. it was made AFTER html4.0 was standardized. no excuse for that type of product.

login or register to post comments

WebTV an excellent example

Submitted by urlborg on August 15, 2001 - 06:09.

HTML 4.0 is not and has never been 'standardized' by any means because absolute position was a completely dumb idea that made no sense within the existing html framework and is simply not html compliant! (read: backward compatible technology) The fact is that only Netscape 6.0-6.1 comes close to supporting the W3c's dreamy CSS 'standard' that has never properly functioned, without extensive workarounds, in any browser! One would have to be insane to publish absolutely-positioned 'html blocks of content' that require scripting to show, hide or 'position' and expect any but a tiny portion of you audience to see any more than a list of elements! IEs clone of 'script'ing is a major security risk, Netscape JavaScript (and styles) can and usually will be turned off or proxy filtered to prevent pop up hell...

As far as WebTV goes, a substantial part of our business is from WebTV users, at no expense to 1200X1600 users because WebTV got it right, by rescaling images and tables automatically to fit within a resolution-crippled screen size, unlike broken, bloatware browsers from Microsoft and Netscape that lack this most basic, simple functionality! I am personally very happy to see competitors ignore WebTV, I like their business!

There is simply NO intelligent excuse why browsers like IE AOL, Netscape and Opera do not automatically scale rendering to accommodate crippled screen resolutions like a simple, basic low-end web appliance can!

login or register to post comments

hasn't been standardized?

Submitted by broFECES on August 15, 2001 - 15:20.

html 4.01 has not been standardized? sure it has!

implementation is a different thing alltogether.
implementation of the standards as a baseline has not yet completely happened, but standards do exist.

but you do have a point (which i was also trying to make) - that resolution should be a non-issue for information sites since we really should be using xml or something along those lines. let the output device handle the display in a manner appropriate to its abilities (such as resizing)

login or register to post comments

The tyranny of 1024 x 768

Submitted by r937 on January 16, 2002 - 08:08.

As if "this website best viewed at 800x600" were not bad enough, many so-called web designers are now insisting that your resolution be 1024x768.

The tyranny of 1024 x 768 is extremely popular at the moment, being linked to by countless weblogs. It has a sidebar link to a google search which turns up 117,000 pages demanding this new resolution. But it's just a rant, a pretty poor one at that, and nowhere near as comprehensive as the above evolt article. To top it off, it's written in 10-pixel font (although the author does apologize for this).

What do we have to do to get those crazy webloggers to link to the far more substantial evolt articles instead?

login or register to post comments

surf the web at 640 x 480...

Submitted by parasite on January 18, 2002 - 18:11.

Couldnt agree more, however, seems many sites do not. I have a session every now and then at 640x480 just to remind myself what it's like. Seems every second site I visit has never heard of "fluid design". Is it really that hard? No. Fluid design is not "fluid" at all if it's only intended to look good at 800x600 and up? I take it no one is future proofing for small displays? How long will it be before every car and plane is riddled with these small screens? Not long my friends, ever been stuck in a traffic jam in LA? Also - it's pretty bad when Yahoo doesnt fit on 800x600 eh? Other site not conforming, MM, Adobe, ACNielson, Altavista, tomshardware, etc etc ... the list goes on.

login or register to post comments

fluid for fun and profit

Submitted by aardvark on January 18, 2002 - 23:02.

Parasite, I agree with you that fluid/liquid designs are no good if they won't scale down as well as up. There are many considerations for developing liquid sites, many of which I address in my article (ooh, blatant article pimping) Liquid Design for the Web. After all, if you're handling for higher resolutions, then why not handle for lower ones as well?

login or register to post comments

Res Depends On The User

Submitted by billabel on January 24, 2002 - 00:07.

One point overlooked is a simple one. Not all users are equal. Each Web site I design is based on the audience that will view it. Many times I find that there is a low-tech audience with older computers and lower resoloutions. In these cases the percentage of 640x480 users are up to 20%, much higher than the 3-5% average most current research suggests.

I think it is critical that we as designers build sites that benefit the people using them. Technologies like XML will allow content to be displayed in phones or pdas, but simple graphic design and layout should still provide for usablity. Any site that is designed to be rendered at a fixed width of more than 590 pixels is going to impair somone, somewhere, probably from now on.

We might take for example books. There are large format books, but there is also a standard size for the masses - paperbacks. They are all the same size. It's convenient and familiar. Larger books tend to be hard to deal with...they are not easy to carry around, they are too tall on the shelves...they are difficult to hold and are easier to read while sitting at a table...

Web sites tend to follow suite. A standard width is something that is familiar and comfortable and most of all usable.

With that in mind, there will always be a time for large format sites and we should create them when it makes sense. But right now the sensible thing to do in most cases is to keep a standard width (dynamic or static) that works well for users with a 640x480 resolution.

login or register to post comments

web sites are not books

Submitted by r937 on January 24, 2002 - 10:30.

i agree with your comments, billable, especially the conclusion ("... that works well for users with a 640x480 resolution") but i must disagree with your analogy

paperbacks are containers (they contain the thoughts that are the book) and paperbacks are standardized on size not to suit the reader, but rather to suit the publisher -- think of the machinery of printing, and shipping, and stocking inventory, etc., and what it would cost if all readers could order the paperback from the publisher in their own choice of sizes!!

the comparable analogy for web sites is the browser window, not the resolution, and we would be better to target how wide the user's window is -- many people prefer 600 pixel windows even though their resolution may be over 1000

still, a paperback's author is not constrained by the physical dimensions of the paperback -- it's easy to devise a layout of words which has you read page 1, then page 99, then page 2, then page 98, and so on (which is how it feels to read a web page with a horizontal scrollbar) -- but i'm glad most authors do not choose to do this to me

you say "a standard [web site] width is something that is familiar and comfortable and most of all usable" and i agree -- i like reading paperbacks when the author has allowed the words to flow into the book size set by the publisher

with web sites, the publisher is the browser, and you'd be right about standard web site widths if every browser could be forced to be maximized to the full resolution

but since users control their browser's width, i doesn't make sense for web site creators to target a "standard" width, because there ain't no such thing

login or register to post comments

Paperbacks and browsers

Submitted by billabel on January 24, 2002 - 11:10.

Thanks for your comments.

Let me clarify what I meant in using my analogy. There tends to be a usable standard book size; the paperback size has been adopted as the mass media standard for distribution. To understand why, if you go to a library for instance, you may find a 100lb dictionary on a roll-around-stand. It's a book. But it's size is not usable to the masses. You can't throw it in your backpack and hop on the train.

So the paperback format was adopted by the publishing industry as a standard. Maybe their press sizes played a role --- but no one can argue the convenience of the size. It just works well.

A web browser displays web sites, in much the same way as paper and binding display written words. They both are mediums. Niether has a standard size set in stone that everyone uses -- and they shouldn't. But, paperback size is the choice of the masses. Therefore, there obviously must be a set width that the masses would prefer to view web pages. Or at least, I think there is one.

No one has the answer yet. But considering that computers are getting smaller, I don't see how larger sizes are going to be usable with the newer technologies. Laptops are very affordable and most now have an 800 x 600 res - I would love to have a PDA with a color screen at 640x480 with voice recognition and I can't imagine viewing a small screen at a higher resolution. It's just too hard on the eyes -- and I'm only 29. Sure we will all have 21" monitors at home or at work one day, but you can't carry those camping. You can't carry those on the train. You can't carry them around in your pocket. Smaller and smaller screens are going to appeal to users for their convenience, just as the paperback provides a small, economical and convenient size for book consumers.

The users are going to define the standard in the end. In my opinion, I believe it is going to be a smaller size rather than a large one. We have to cater to them, eventually they will demand that we give them what they want. Maybe it will be an 800x600 size, but more likely it will fall around 640x480.... we'll see.

login or register to post comments

Think of the future

Submitted by jsp on January 30, 2002 - 16:56.

Here's the Jan 2002 TheCounter.com resolution stats:
  • 800x600: 52%
  • 1024x768: 34%
  • 640x480: 4%
  • 1280x1024: 3%
  • 1152x864: 2%
640 is dying, as it should. It’s not dead yet, but consider: Microsoft has sold over 17 million copies of WinXP as of this writing. That O/S defaults to 16-bit color at 800x600. (You can get lower, but only through advanced options.)

As for PDAs, and, worse, car and phone displays: don’t even think that your tables-based layout is appropriate for those devices. Use a smarter approach. Consider clipping languages, XML/XSLT on the server, and in general using semantic mark-up to say what’s important and what order it should be shown in. In short, think in terms of accessibility for text browsers. That’s about the highest level of control you can expect. (Anything on a phone is crap right now anyway.) Remember, here the issue is one of safety: for cars and phones, it is essential that the content be as simple and clear as possible. Confusion could equal injury.

But take heart. All of this discussion of 17" monitors and 21" monitors and all the fun stuff in between forgets one other concept: the 72/96dpi standard is also changing. On one end, Microsoft (with ClearType) and Adobe (with CoolType) have created approaches that work at the sub-pixel level to make text sharper and easier to read. Microsoft’s version is included in Windows XP.

That’s nice, but the exciting stuff is happening at the other end: improved LCD manufacturing. Today, an average 21" monitor may run 1600x1200 -- about 1.92 million pixels. IBM now sells an LCD monitor that has over 9.2 million pixels in a 22.2" display. That’s 30 times 640x480. True, the monitor is very, very expensive, but you can buy one right now. It’s not a prototype.

So in short, by all means use liquid layouts so the user can choose the width. But don’t think you can solve every layout problem with tables alone, and be ready for the time when your graphics will have to be much higher resolution to use the same amount of physical space. (And don't forget the wildcard: vector graphics!)

login or register to post comments

Woot

Submitted by Markavian on July 8, 2002 - 08:31.

Too much information, information overload. etc. etc. My eyes started going fuzzy round about the second set of %'s..

These days I design for 800x600.. for reasons to do with content spacing and readability. Not because lots of people might be using it.

I don';t konw if you mentioned it above, but monitors which run at 640x480.. the 'default settings' probably also have a colour range of 16 colours.

I'm sorry, but I won't be designing websites to match the 16 colour window's palette.

I design websites for my self and friends, and the odd visitor.

I do know people who run 800x600 at 16 million, and these people use the internet frequently.

I'll remember the little tip about printing pages.

This page was supposed to be 'scan easy'. I'd prefer yet smaller still paragraphs.

login or register to post comments

Design issue:

Submitted by Markavian on July 8, 2002 - 08:37.

That thing about tables..

One option is:

Define your smallest resolution. I pick 800x600. E.g. make the websitel fit on any screen 800 pixels wide, or wider.
Therefore, make the table width will be about 700 pixels wide. All content will fit within this boundary.

Center the table

Content will be easily readable. Positioned as you want it. Having a larger monitor/res. will not provide advantage/disadvantage.

A good example of what I'm talking about is at http://mkv25.net

~ Markavian

login or register to post comments

the numbers

Submitted by aardvark on July 8, 2002 - 17:35.

Markavian, this article isn't about our preferences as designers, but recognizing how some users surf. For instance, you suggest that people running at 640x480 are also running at 16 colors. But my own research shows that, even two years ago, the average user at 640x480 actually ran at 16-bit — or thousands of colors.

Youi also say you design for 800x600 due to content spacing and readability. I'd be interested to hear more detail about that. For instance, what increases in comprehension or readability have you gotten? Have you performed user testing? I suppose if, as you say, you only design for your friends, you really don't even need to worry about any of this, however.

I'm not sure about your "scan-easy" comment. Do you mean the layout, or the content is too large/wide/something?

login or register to post comments

Design issue

Submitted by urlborg on July 9, 2002 - 12:29.

I agree with you aardvark, designing for a sub-480 column width is nonsense in this day and age. As far as PDwhatnots are concerned, they can all line up for the garbage can until they develop their own means of displaying website content, if it's what they intend to attempt to do.

If WebTV can design the software graphics/display reduction technology to cope with larger image and table content within their severe limitations, then PDA thingy-manufacturers can also do likewise.

This is kind of like the strange issue of braille newspapers, or magazines, recorded vocally on audio tape!

Our research has shown that column widths in excess of 700 pixels at the 10-12 pt font sizes promote eyestrain, and are grossly inneficient in conveying information through luminescent presentations, as do those at less than 300. (these!)

Scrolling is not analagous to page-turning, and a presentation that relies on scrolling is likely to be left unexplored. Remember that scrolling also get's rendered in so many unpleasant fashions on many cheaper graphics systems, and with poor software interface, that users often complain about trying to follow a written thought from framed altitude to framed altitude.

We've found that 800X600 seems to be a nearly ideal page size for a multitude of reasons, including print compatability, proportional graphics file GIF size/JPEG compression loss, usability, read and browseability and especially background image versatility. Images scaled to fit sub-480 column widths can't even achieve near-TV resolution quality.

With so much going for it, it's unlikely that it will be displaced any time soon. As you've noted those that use 1152 X 764 and larger screen sizes and couldn't live without them, still naturally prefer an 600-ish width for readable text formatting.

While this big green band of wasted space I'm now looking at down the center of my screen may seem cute, anybody can see how difficult it is to follow this thread of half-sentence wide comments!

login or register to post comments

green band of wasted space?

Submitted by aardvark on July 9, 2002 - 13:15.

Not sure I'm following you there. This site is liquid, so the page should expand to fill your window, as it does mine.

As for PDAs and the like, I'm not willing to tell users to stuff their platforms without a really good reason, and since a liquid site can well accomodate a PDA user, it's worth considering. Not sure how you find that a layout for 800x600 prints better, at least not without a print CSS file. All too often, hard-coded widths over 600px just don't fit on a portrait sheet of paper.

login or register to post comments

"Easy reading"

Submitted by Markavian on July 9, 2002 - 17:07.

I read somewhere:
  • "Do all web designers have near perfect eyesite? 'cause I don't"
  • ..

    In reference to people (like me) using size 10 fonts and smaller. Where I'm typing now, is size 10/smaller.. its also quite late, I'm straining my eyes.

    I have done no survey testing, I just make something, and if it works for me I keep it.

    I think we need a new topic, about web design . About making sites which are convinient for people to use. e.g. ease of readability, navigatable navbars, and sensible use of graphics. Then people could put forward ideas and examples of good websites; things that looked good and worked...
    ...as well as bad things such as annoying blinking things and large, blank, 'useless areas'..

    ::Looks at green bar on the right::

    Maybe I'll type up my first article tommorow.

    login or register to post comments

    resolution

    Submitted by skquinn on June 14, 2003 - 18:57.

    I rarely surf at full screen. My usual browser window has a usable size of about 985 x 570 though I've been known to use smaller or larger in certain circumstances.

    It was a huge irritant to me at one time that I could make my browser window as big as I wanted and a lot of sites would sit in only the leftmost 600-640 pixels' worth. Thankfully it seems those days are behind us; sites like this one seem to get it mostly right but here, at least, font size does seem to be a little on the small side (thankfully Konqueror has a minimum font size feature).

    Based on what I have seen, I think the entire concept of designing for any one resolution at the expense of others is rather flawed (and the new portable devices are helping make this into cold reality); hopefully, the next generation of CSS with technologies like SVG will help to make resolution less relevant by allowing more for gracefully rescalable images, something we have needed for years.

    login or register to post comments

    another take

    Submitted by jasonscherer on September 4, 2003 - 18:59.

    I'm currently using an old laptop from 1998 and just tonight decided to go down from 800x600 to 640x480 because of eyestrain. Well, the thing about laptop screens (LED's) is that they are really designed to be viewed at only one resolution -- the resolution of the actual hardware. In other words, the screen pretty much has 800 diodes across and 600 diodes down. So you can't view at anything higher than that. In order to view at a resolution lower than that the video driver has to fake you out a bit and compensate. For example, you make three pixels look like two by dimming the middle one a bit, etc.

    Why am I bothering to talk about this in detail in response to an article about usability? Well, interestingly enough, my entire screen is now very pleasantly fuzzed out with this soothing anti-aliasing that's pervasive across the whole display. It's not just the text -- every single dang thing on the screen is a bit blurred -- and I'm finding this to be the visual equivalent of a nice hot bath after a hard day at work.

    The point being? The relentless pursuit of more pixels, bigger monitors, faster systems, higher, stronger, longer is actually doing less good for me right now than a kludgy workaround from 5 years ago. And right now some engineer in the Valley is trying to think of a way to get rid of that kludge so that when I buy a laptop in 2005 I will have no choice but to have the crisp, caffinated clarity of what they think I want burned into my retinas whether I like it or not.

    login or register to post comments

    nobody here gets the point!

    Submitted by milky on September 5, 2003 - 05:45.

    There is no need to guess a users screen resolution - HTML is not the abbreviation for HyperPictureMarkupLanguage!! The only important screen resolution is 80x25.

    login or register to post comments

    agreed

    Submitted by skquinn on September 5, 2003 - 17:11.

    Agreed to a point, though personally I think the most important screen resolution is "none at all". (i.e., Googlebot, Scooter, Gulliver, and similar indexing robots)

    login or register to post comments

    Skqinn...

    Submitted by Markavian on September 6, 2003 - 05:02.

    What if you don't want a page to be listed on a search engine?

    Is it still of massive important to script your code appropriately for something that doesn't care about the layout and design of a page?

    login or register to post comments

    reply

    Submitted by skquinn on September 6, 2003 - 19:15.

    Yes, it is still important, but for the vast majority of sites, search engine listings are either the primary source or a very important source of traffic.

    login or register to post comments

    'Most Important'

    Submitted by Markavian on September 7, 2003 - 04:41.

    Okay, so you've designed your website so that Googlebot can read it, and categorise it properly?

    Whos the most important target audience after that? Humans maybe?
    What resolution should they be subjected too?
    Should they be reading fixed width sites, or fluid layout sites.

    As the article highlights, should you still be designing for 640x480 screens?

    That is of course if you care about the human side of web browsing, skquinn.

    login or register to post comments

    the entire concept

    Submitted by skquinn on September 7, 2003 - 07:27.

    I believe the entire concept of locking down a layout to a specific resolution is flawed. It frequently creates many, many more problems than it solves, and often is not even necessary. My answer to what resolution to design for is "no one resolution in particular". Or, put more aptly, don't design for 640x480 any more than, say, 80x25 text mode or 2048x1536.

    login or register to post comments

    Times change, but the concept doesn't

    Submitted by aardvark on September 7, 2003 - 07:46.

    It's been four years since I wrote the article now, and while the stats have changed about who uses what resolution, the general concept still applies — be aware of what shutting out a particular resolution, particularly lower ones, can do to your users and the experience of your site.

    Two articles that I've written for evolt.org since then suggest how you can determine the resolution of users at your site, which is better than relying on someone else's stats, and how you can design a page to be liquid to scale up and down to meet the user's window sizes:

    login or register to post comments

    and it was eaten by the black hole!

    Submitted by genckas on September 15, 2003 - 11:56.

    It is dying but that does not mean that we must not design in 640. There are ways of detecting resolution and then delivering the appropriate site resolution. Of course this means that there are quite a few page designs...ah well... genc

    login or register to post comments

    how many designs is too many?

    Submitted by r937 on September 15, 2003 - 12:45.

    genc, do you believe in forcing your site visitors to maximize their browser windows? if i have 1280x1024 but i choose to have my browser at less than maximum, will you deliver a page design that assumes 1280x1024? that's pretty inconsiderate of you

    learn liquid, deliver one design to all resolutions

    rudy
    http://rudy.ca/

    login or register to post comments

    two is enough...

    Submitted by genckas on September 15, 2003 - 14:55.

    I see your point. Of course I wouldn't go as far as having a design for every specified resolution. Rather there would be one for 640 and then the rest. If the site is informative, e.g. real-time satelite data on polar caps, it is good if it were accessible by all possible means, 640 resolution, text browsers like Lynx, cross browser compatibility etc. That is the way I think of the 640. Not every resolution a modified design. I haven't been using 640 ever since the days of 3.11 but if the site contains important information, I would still design around it. On the other hand, if the site is the official Tomb Raider 3 site then I would shove 640 away, it cripples ones creativity. genc

    login or register to post comments

    One design multiple display sizes

    Submitted by cpmx on October 14, 2004 - 15:27.

    If you use a liquid layout based on percentages, your site will easily adapt to different display sizes. Don't forget to use relative units for your fonts too. Personally I have used this approach on my website which, with the exception of images, is totally liquid capmex.biz. I remember when I was designing my template, I tested on an old 640x480 black and white monitor, just to see how it'll look.

    login or register to post comments

    The access keys for this page are: ALT (Control on a Mac) plus:

    evolt.orgEvolt.org is an all-volunteer resource for web developers made up of a discussion list, a browser archive, and member-submitted articles. This article is the property of its author, please do not redistribute or use elsewhere without checking with the author.