spazmaster
05-13-2004, 04:01 AM
Heya fella's and gals,
anyways, the issue i wanted to discuss with you guys is the domain of Sound and Websites.
Different Expectations
When i turn on my TV, i'm expecting to hear sound. When i visit a website i do not expect to hear sound, and when i look at my past behaviour, i see that i nearly always turn off the on-load sound on any website the second i can. I'm scanning for the mute sound! My engagements with TV or with a website, are accompanied with totally different expectations.
Selling a product
We just launched a new website for a client (www.radioelizabeth.com) who is a voice artist. The client wants sound on-load, which i can understand. I actually agree with her, because people visiting her site will be mainly people interested in a voice artist and are coming there to get an impression of who she is, what she stands for, and Elizabeth serves them her "sound" instantaneously. Because of how the website unfolds her sound adds to the experience by supporting the animations that the site opens with.
Permission
My colleague however disagrees. He argues that we should go for "best practice" and advise along that path. People visiting a website should always be offered the decision of triggering the sound instead of being forced to hear sound. The user has a better experience, being acknowledged that permission should be given for presenting sound in a website.
Looking at my own behaviour i know i want to control the fact if i'm gonna hear sound or not, and found it annoying when sound is on-load, but on the other hand i think we're looking at a taregt group who will shift expectations from a normal website, and be OK since its a wbesite of a VOICE artist.
Go between
CyanBlue had a good remark, offering the solution of using Shared Object to play the sound on-load the first time the user visits the site, but cancels the on-load the second time the user enters the site. This could avoid the annoyance usually created by repeat visits to a website accompanied by repeats of the same sound over and over again.
However this does defy the "permission based" expectation that user experience wise seems the best practice.
Best Practice
Is there a best practice in this? Regardless of what kind of website we're dealing with? What do you guys think? I was hoping to get a discussion going on so there would be a chance to offer eachother insightful principles/info.
looking forward to hear from you guys!
anyways, the issue i wanted to discuss with you guys is the domain of Sound and Websites.
Different Expectations
When i turn on my TV, i'm expecting to hear sound. When i visit a website i do not expect to hear sound, and when i look at my past behaviour, i see that i nearly always turn off the on-load sound on any website the second i can. I'm scanning for the mute sound! My engagements with TV or with a website, are accompanied with totally different expectations.
Selling a product
We just launched a new website for a client (www.radioelizabeth.com) who is a voice artist. The client wants sound on-load, which i can understand. I actually agree with her, because people visiting her site will be mainly people interested in a voice artist and are coming there to get an impression of who she is, what she stands for, and Elizabeth serves them her "sound" instantaneously. Because of how the website unfolds her sound adds to the experience by supporting the animations that the site opens with.
Permission
My colleague however disagrees. He argues that we should go for "best practice" and advise along that path. People visiting a website should always be offered the decision of triggering the sound instead of being forced to hear sound. The user has a better experience, being acknowledged that permission should be given for presenting sound in a website.
Looking at my own behaviour i know i want to control the fact if i'm gonna hear sound or not, and found it annoying when sound is on-load, but on the other hand i think we're looking at a taregt group who will shift expectations from a normal website, and be OK since its a wbesite of a VOICE artist.
Go between
CyanBlue had a good remark, offering the solution of using Shared Object to play the sound on-load the first time the user visits the site, but cancels the on-load the second time the user enters the site. This could avoid the annoyance usually created by repeat visits to a website accompanied by repeats of the same sound over and over again.
However this does defy the "permission based" expectation that user experience wise seems the best practice.
Best Practice
Is there a best practice in this? Regardless of what kind of website we're dealing with? What do you guys think? I was hoping to get a discussion going on so there would be a chance to offer eachother insightful principles/info.
looking forward to hear from you guys!