> The question keeps coming up about how long people are willing to wait for
> something to load. Is there such a thing as an acceptable load time?
Guess that's all already said, but the "10 seconds rule" continues to
apply anyway, and "as fast as possible, no matter what" will remain an
importa
On Apr 19, 2008, at 7:14 AM, Bruno Figueiredo wrote:
> I would suggest you to put up a static version of what they're
> waiting to load with a loading bar on top. That way users get a
> general sense of what's to come and if it's worth it or not. Kinda
> of what we did back in the days with no bro
It's all about managing expectations, by default I consider 2-3
seconds of perceived waiting max, anything longer should be choose
your own adventure (e.g. low res, high fi) and or using bandwidth
detection to autoroute.
high experience is engaging the user in a seamless narrative and or
flow stat
I agree with Will. The mouse pointer is kind of a digital extension to
your arm. I think it reflects more what users are thinking since they
can understand what's hot or not by hovering the pointer on top of
it.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the n
" I'm currently working on a flash-heavy 'experiential' site, where the
flash
is mostly concentrated in areas of light information and entertainment
rather than utility/functional sections."
One thing I would caution against - and I have heard/seen this over and over
to the point of annoyance, is
I would suggest you to put up a static version of what they're
waiting to load with a loading bar on top. That way users get a
general sense of what's to come and if it's worth it or not. Kinda
of what we did back in the days with no broadband where we used
lowres versions of the images to be loade
Robert is right!! Make sure that the content is worth waiting for.
Add some interactive to your site while their are waiting...
Such as a simple mind games.. or a transition of images.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://ww
Try eliminating the wait altogether by using some smart load
techniques. Use the downtimes where users are not downloading
anything to download the next part of your application in the
background. Remember that your browser caches SWFs.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
quote: 2. Make sure the user knows what s/he's waiting for so s/he
can decide whether or not to do so
Dont forget SWF is a streaming file format, so you can show certain
parts of the content while waiting for others to load to help the
user understand what it is that they are waiting for.
. . .
It may be a good idea to include additional content and/or interactive
imagery onto the page so that even if the main content is loading, the
user still has something to view while waiting.
Otherwise, Leandro's comment holds true. Adding a "Skip" button
gives the user(s) the option to bypass the l
Another "trick" I usually do is to compare the loading time, how
long the animation will last, in relation to how big is the flash
file:
-Depending on the users bandwidth, you wouldn't have to make them
wait for the whole animation to be loaded before playing: you could
have it play once "x" % of
>
> Does anyone have general rules of thumb to share?
>
1. Make sure the content is worth waiting for
2. Make sure the user knows what s/he's waiting for so s/he can decide
whether or not to do so
3. Design a loading piece that makes the wait appear shorter than it is
This last one can be done in
First of all, you need to involver the user. Nobody will wait if the
content loading isn't interesting or important to them. So, make
sure that the loading content is something that user needs.
If possible, skip it. One option is to insert a "skip transition"
button, so the user don't need to wait
Hi all,
I'm currently working on a flash-heavy 'experiential' site, where the flash
is mostly concentrated in areas of light information and entertainment
rather than utility/functional sections.
For some sections, there is some loading that needs to happen before a
motion sequence/transition into
14 matches
Mail list logo
