<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How Big Is Too Big?</title>
	<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Sat, 06 Sep 2008 06:02:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-913</link>
		<author>Andrew Faulkner</author>
		<pubDate>Fri, 21 Apr 2006 09:34:18 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-913</guid>
					<description>I try to encorporate what I assume are the maximum and minimum screen sizes in my designs. Most of the time this means using a 'liquid layout. I do tend to 'stop' a design at large widths as readability becomes an issue.

One point to take on board is that browser stats give the wrong impression. Seeing that 75% of fadtastic users have a resolution of 1280 x 1024 may not mean that 75% are using their browser in full-screen mode. They may also have sidebars open making the viewport smaller.</description>
		<content:encoded><![CDATA[<p>I try to encorporate what I assume are the maximum and minimum screen sizes in my designs. Most of the time this means using a &#8216;liquid layout. I do tend to &#8217;stop&#8217; a design at large widths as readability becomes an issue.</p>
<p>One point to take on board is that browser stats give the wrong impression. Seeing that 75% of fadtastic users have a resolution of 1280 x 1024 may not mean that 75% are using their browser in full-screen mode. They may also have sidebars open making the viewport smaller.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Yas</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-918</link>
		<author>Yas</author>
		<pubDate>Fri, 21 Apr 2006 17:06:07 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-918</guid>
					<description>I try to follow the 12" Powerbook rule. If it doesn't look good on that screen, it's probably not the best design.

Not that our current design passes with flying colors, but I always try to keep our small-screened readers in mind.</description>
		<content:encoded><![CDATA[<p>I try to follow the 12&#8243; Powerbook rule. If it doesn&#8217;t look good on that screen, it&#8217;s probably not the best design.</p>
<p>Not that our current design passes with flying colors, but I always try to keep our small-screened readers in mind.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew W</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-919</link>
		<author>Andrew W</author>
		<pubDate>Fri, 21 Apr 2006 18:26:00 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-919</guid>
					<description>The 12" Powerbook rule is a good idea. Even if you're a designer with a huge screen at home, you may also have a laptop and almost certainly have a smallish monitor at work. That's how it is for me at least.</description>
		<content:encoded><![CDATA[<p>The 12&#8243; Powerbook rule is a good idea. Even if you&#8217;re a designer with a huge screen at home, you may also have a laptop and almost certainly have a smallish monitor at work. That&#8217;s how it is for me at least.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darren Hoyt</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-924</link>
		<author>Darren Hoyt</author>
		<pubDate>Sat, 22 Apr 2006 02:43:10 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-924</guid>
					<description>Take it for what it's worth, but this year I began designing for a width of about 820px, usually centered. It leaves the 800x600 standard behind (most new machines are shipping with 1024 resolution these days anyway), but does not get so close to 1024 that folks with laptops must scroll horizontally. Liquid layout for me is just too big a risk as I see monitors getting larger -- reading text more than about 8" across is too difficult for the eye to follow line to line. The average paperback book is maybe 6" wide and for good reason.</description>
		<content:encoded><![CDATA[<p>Take it for what it&#8217;s worth, but this year I began designing for a width of about 820px, usually centered. It leaves the 800&#215;600 standard behind (most new machines are shipping with 1024 resolution these days anyway), but does not get so close to 1024 that folks with laptops must scroll horizontally. Liquid layout for me is just too big a risk as I see monitors getting larger &#8212; reading text more than about 8&#8243; across is too difficult for the eye to follow line to line. The average paperback book is maybe 6&#8243; wide and for good reason.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Gomi</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-930</link>
		<author>Gomi</author>
		<pubDate>Sat, 22 Apr 2006 12:32:46 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-930</guid>
					<description>About 20% of the visitors on my more popular sites use a screen resolution of 800x600px or lower so I still use 800x600 as the base resolution for most of my designs. Liquid layout is good for crossing the resolution divide but I personally feel a fixed width site provides more control and compatibility with that dinosaur, ie, plus I have yet to see a liquid layout site that looks good and still be very usable on huge monitors (20"+). Using background image 'trickery' is one of the techniques that can be employed effectively for users with bigger displays on a 'small width' site.</description>
		<content:encoded><![CDATA[<p>About 20% of the visitors on my more popular sites use a screen resolution of 800&#215;600px or lower so I still use 800&#215;600 as the base resolution for most of my designs. Liquid layout is good for crossing the resolution divide but I personally feel a fixed width site provides more control and compatibility with that dinosaur, ie, plus I have yet to see a liquid layout site that looks good and still be very usable on huge monitors (20&#8243;+). Using background image &#8216;trickery&#8217; is one of the techniques that can be employed effectively for users with bigger displays on a &#8217;small width&#8217; site.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan Van Den Rym</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-942</link>
		<author>Johan Van Den Rym</author>
		<pubDate>Sun, 23 Apr 2006 14:06:52 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-942</guid>
					<description>you can serve a different stylesheet to users using eg 800 *600 design, wih Javascript you can add a listener which detects browser dimension and load the stylesheet accordingly.</description>
		<content:encoded><![CDATA[<p>you can serve a different stylesheet to users using eg 800 *600 design, wih Javascript you can add a listener which detects browser dimension and load the stylesheet accordingly.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Kevin Cannon</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-952</link>
		<author>Kevin Cannon</author>
		<pubDate>Mon, 24 Apr 2006 13:47:20 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-952</guid>
					<description>Wait a second. You do your code first? That seems kind of backward to me, perhaps you could explain your process.</description>
		<content:encoded><![CDATA[<p>Wait a second. You do your code first? That seems kind of backward to me, perhaps you could explain your process.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-953</link>
		<author>Andrew Faulkner</author>
		<pubDate>Mon, 24 Apr 2006 15:46:36 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-953</guid>
					<description>I'd also be interested to hear how/why you code first. Please tell us how you do you websites. Just curious.</description>
		<content:encoded><![CDATA[<p>I&#8217;d also be interested to hear how/why you code first. Please tell us how you do you websites. Just curious.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steve C.</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-956</link>
		<author>Steve C.</author>
		<pubDate>Mon, 24 Apr 2006 20:27:25 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-956</guid>
					<description>(off topic...)

"Liquid layout for me is just too big a risk as I see monitors getting larger — reading text more than about 8″ across is too difficult for the eye to follow line to line."

Yep.  For this reason I would recommend you use a max-width.  This way you can cap the width to keep it from getting too out of hand.  There are even ways of getting max-width to work reliably in IE (gasp!)

http://www.cameronmoll.com/archives/000892.html</description>
		<content:encoded><![CDATA[<p>(off topic&#8230;)</p>
<p>&#8220;Liquid layout for me is just too big a risk as I see monitors getting larger — reading text more than about 8″ across is too difficult for the eye to follow line to line.&#8221;</p>
<p>Yep.  For this reason I would recommend you use a max-width.  This way you can cap the width to keep it from getting too out of hand.  There are even ways of getting max-width to work reliably in IE (gasp!)</p>
<p><a href="http://www.cameronmoll.com/archives/000892.html" rel="nofollow">http://www.cameronmoll.com/archives/000892.html</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-957</link>
		<author>Steven Teskey</author>
		<pubDate>Tue, 25 Apr 2006 00:12:20 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-957</guid>
					<description>I (as of recently) believe that most of the beauty in a webpage is in how the information is arranged. The best sites are harmonies of graphical and informational representation. It's easy to forget that the infromation must be the focus of the website when heavy graphics are used. Hopefully that may justify my methods. I've been asked to explain my methods of design, so I shall endulge (even though I don't quite think that the comments section is the place for this.

I have a habit of being somewhat sporadic, and as I really only design unformally (for myself, or for no money), I tend to change things up a lot. When I say "a lot" I mean entire layouts on a whim. To combat this I tend to start off by determining what type of information I'll be displaying, how much information, and the best methods of displaying such information. From there I create a layout, sounds strange I know, but with an imagination like mine it's just easier to get what I originally wanted without straying. After the layout is complete, as in all information has been displayed in a manner that's best suited to it, I then add the graphical touches. I do minor changes afterwards, so that there isn't any heavily conflicting design work.</description>
		<content:encoded><![CDATA[<p>I (as of recently) believe that most of the beauty in a webpage is in how the information is arranged. The best sites are harmonies of graphical and informational representation. It&#8217;s easy to forget that the infromation must be the focus of the website when heavy graphics are used. Hopefully that may justify my methods. I&#8217;ve been asked to explain my methods of design, so I shall endulge (even though I don&#8217;t quite think that the comments section is the place for this.</p>
<p>I have a habit of being somewhat sporadic, and as I really only design unformally (for myself, or for no money), I tend to change things up a lot. When I say &#8220;a lot&#8221; I mean entire layouts on a whim. To combat this I tend to start off by determining what type of information I&#8217;ll be displaying, how much information, and the best methods of displaying such information. From there I create a layout, sounds strange I know, but with an imagination like mine it&#8217;s just easier to get what I originally wanted without straying. After the layout is complete, as in all information has been displayed in a manner that&#8217;s best suited to it, I then add the graphical touches. I do minor changes afterwards, so that there isn&#8217;t any heavily conflicting design work.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Chris Williams</title>
		<link>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-987</link>
		<author>Chris Williams</author>
		<pubDate>Fri, 28 Apr 2006 15:35:11 +0000</pubDate>
		<guid>http://fadtastic.net/2006/04/21/how-big-is-too-big/#comment-987</guid>
					<description>[quote]With lots of users adopting a larger screen area I find it easy to believe that no one uses anything smaller than 1024×768[/quote]

I find this statement quite shocking honestly.  

Yes quite a few websites seem to be embracing the 1024 resolution as a minimum width lately - but this is usually from sites in the web design community where their audience is very computer-savvy (this very website for example).

When moving away from this kind of audience, I think the number of users still using 800x600 is quite high.  One set of website stats I have access to for instance (which is from a global website, with a very wide and varied audience) can see 800x600 at something like 20%.  If that website is receiving 10,000 visitors a day, should we then make 2000 of those scroll horizontally?!

Again this all comes down to "horses for courses" - where a higher screen res may be acceptable for one website but not another.

Personally, unless the website has a very computer focused audience I still think it is too soon to be disregarding the 800x600 users.</description>
		<content:encoded><![CDATA[<blockquote><p>
With lots of users adopting a larger screen area I find it easy to believe that no one uses anything smaller than 1024×768</p>
</blockquote>
<p>I find this statement quite shocking honestly.  </p>
<p>Yes quite a few websites seem to be embracing the 1024 resolution as a minimum width lately - but this is usually from sites in the web design community where their audience is very computer-savvy (this very website for example).</p>
<p>When moving away from this kind of audience, I think the number of users still using 800&#215;600 is quite high.  One set of website stats I have access to for instance (which is from a global website, with a very wide and varied audience) can see 800&#215;600 at something like 20%.  If that website is receiving 10,000 visitors a day, should we then make 2000 of those scroll horizontally?!</p>
<p>Again this all comes down to &#8220;horses for courses&#8221; - where a higher screen res may be acceptable for one website but not another.</p>
<p>Personally, unless the website has a very computer focused audience I still think it is too soon to be disregarding the 800&#215;600 users.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
