<?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"
	>
<channel>
	<title>Comments on: All about preloader - Part I: What is a preloader?</title>
	<atom:link href="http://flashrevolution.net/all-about-preloader-part-i-what-is-a-preloader/feed/" rel="self" type="application/rss+xml" />
	<link>http://flashrevolution.net/all-about-preloader-part-i-what-is-a-preloader/</link>
	<description>Another Singapore Flash User Group</description>
	<pubDate>Fri, 21 Nov 2008 03:45:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Shang</title>
		<link>http://flashrevolution.net/all-about-preloader-part-i-what-is-a-preloader/#comment-62</link>
		<dc:creator>Shang</dc:creator>
		<pubDate>Mon, 14 Apr 2008 03:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://flashrevolution.net/all-about-preloader-i-what-is-a-preloader/#comment-62</guid>
		<description>Yes, I agree with you that it's all about reaching a balance of being not boring and not delaying the real content either.</description>
		<content:encoded><![CDATA[<p>Yes, I agree with you that it&#8217;s all about reaching a balance of being not boring and not delaying the real content either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevin</title>
		<link>http://flashrevolution.net/all-about-preloader-part-i-what-is-a-preloader/#comment-60</link>
		<dc:creator>kevin</dc:creator>
		<pubDate>Sun, 13 Apr 2008 18:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://flashrevolution.net/all-about-preloader-i-what-is-a-preloader/#comment-60</guid>
		<description>I agree with you, that the preloader should be small in size, 

I myself, have come across situations where a designer would like to enhance the preloader, by adding something that helps improve the messaging of the website,

often we have to compromise on what will be displayed, during the preloading phase.

Designers and Art Directors, will always want to provide the best overall experience possible, but it is times like these, that trade offs must be made.

The problem of course is coming to an agreement about what is the "acceptable" tradeoff, as well as what is would provide the "best" overall experiance.


On the point of the preloader getting less important, I disagree on that point

I agree with you that higher bandwidth, allows microsites to load faster, but I also notice the fact, microsites increase in file size and richness with the bandwidth as well, which in turn make the preloading "longer" =P.

As long as we keep trying to give the best possible experiance within a reasonable waiting time, then I think the sight of the preloader is here to stay.

Another reason, comes from the best argument, I have heard from an Art Director, regarding putting additional content into the preloader.

His point was that a preloader is often the very first thing you see on a website, as such it should help to sell whatever the Microsite is trying to say.

As its value is akin to the front page headline of a newspaper.

I have to agree with him on that point and in that context. and as you can guess, I had a long an interesting discussion with him before we came to an agreement for that project.

I think that no one is against adding content that enhances the experiance or messaging of a website, the problem arises, when you trade off too much for too little.

If the additional content has a strong messaging element, I would try to engage the Creative to see if a compromise can be made.

But if the preloaders additional size, is increased beyond what is reasonable like in your case, loading of a preloader, just to make it more beautiful, 

then I would strongly argue against it, as the increased filesize would drag down the experiance of the website. without adding an equal or greater value to the experiance/messaging of the website.</description>
		<content:encoded><![CDATA[<p>I agree with you, that the preloader should be small in size, </p>
<p>I myself, have come across situations where a designer would like to enhance the preloader, by adding something that helps improve the messaging of the website,</p>
<p>often we have to compromise on what will be displayed, during the preloading phase.</p>
<p>Designers and Art Directors, will always want to provide the best overall experience possible, but it is times like these, that trade offs must be made.</p>
<p>The problem of course is coming to an agreement about what is the &#8220;acceptable&#8221; tradeoff, as well as what is would provide the &#8220;best&#8221; overall experiance.</p>
<p>On the point of the preloader getting less important, I disagree on that point</p>
<p>I agree with you that higher bandwidth, allows microsites to load faster, but I also notice the fact, microsites increase in file size and richness with the bandwidth as well, which in turn make the preloading &#8220;longer&#8221; =P.</p>
<p>As long as we keep trying to give the best possible experiance within a reasonable waiting time, then I think the sight of the preloader is here to stay.</p>
<p>Another reason, comes from the best argument, I have heard from an Art Director, regarding putting additional content into the preloader.</p>
<p>His point was that a preloader is often the very first thing you see on a website, as such it should help to sell whatever the Microsite is trying to say.</p>
<p>As its value is akin to the front page headline of a newspaper.</p>
<p>I have to agree with him on that point and in that context. and as you can guess, I had a long an interesting discussion with him before we came to an agreement for that project.</p>
<p>I think that no one is against adding content that enhances the experiance or messaging of a website, the problem arises, when you trade off too much for too little.</p>
<p>If the additional content has a strong messaging element, I would try to engage the Creative to see if a compromise can be made.</p>
<p>But if the preloaders additional size, is increased beyond what is reasonable like in your case, loading of a preloader, just to make it more beautiful, </p>
<p>then I would strongly argue against it, as the increased filesize would drag down the experiance of the website. without adding an equal or greater value to the experiance/messaging of the website.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
