What is the significance of start-up sound of a system, like mobile phones, operating systems etc.?
What aspect of user experience does it enhance?
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
My understanding was that it came from a time when startup could take a while, during which the user's attention would be elsewhere and therefore worth notifying them when the computer was ready for use.
Something similar was mentioned in answer to another question:
The Operating System took so long to start up that the chime notified people that it was worth bothering to come back to the computer from, e.g., making a coffee. (Should we use a sound/jingle when users arrive on our site or open our app?)
According to comments made by Microsoft to Mashable, the startup sound was removed in Windows 10 because there's no need to draw attention to startup:
When we modernized the soundscape of Windows, we intentionally quieted the system. Using Windows 10, you will only hear sounds for things that matter to you. We removed the startup sound because startup is not an interesting event on a modern device. Picking up and using a device should be about you, not announcing the device's existence.
Part of it is iconic branding, much like putting the logo on the boot screen. I can still remember the startup sound from windows xp and playstation one.
To give auditory feedback to the user that the system has started loading.
Here are 3 reasons why:
Prevent users from hitting the power button multiple times.
Users should not wonder whether the system is starting or not. If there was no starting sound how would users know that the system has successfully started? They might press the power button a couple of times not knowing that the system is already starting which can cause loss of information and a lot of headaches;
Display not working during repairs
During hardware repairs when technicians haven't connected display or the display is not working and cannot get visual feedback. In this situation auditory feedback comes in very handy.
Cue for visually impaired (@Devin answer)
Visually impaired people rely on hearing and touching when trying to understand the environment around them. If there are no auditory(sound) or haptic(touch/vibration) cues they won't know what is happening with the device.
Beeps during POST are there to help with troubleshooting. Think of it like debugging: if you can't tell why your script isn't working or where, it helps to have it echoing its status along the way in a very verbose manner so it becomes apparent where the issue is. It's like a ping.
POST does a lot of simple things very quickly to test itself (this is all in BIOS so it's actually the motherboard firmware testing itself, and its associated components like processor and memory) like loading basic hardware drivers to talk with other components, and verifying that its own hardware such as the speaker works with a quick beep.MIDI (Talking about the speaker on the motherboard itself here, not the auxiliary speakers you plug in to the back.)
So typically, the computer makes a "beep" only after it has tested and loaded the most-basic-of-the-basics that make it possible for it to "beep". (i.e. indicates successful POST) Basically it is the response to your ping on the power button, "Hello?", "Yes, Hello! I have power and my basic hardware is functional."
So a post-POST beep is there to enhance the technician's experience, or the technical-user's.
Consider the example: You and I have just received the parts to build a new computer, so we unbox the motherboard to perform a benchtest to verify everything is functional first. We power on the system, and get no picture.
Here's a perfect example why those beeps are so important: if we get no beep, what could be wrong? 1) POST did not complete successfully, 2) Speaker hardware is damaged, 3) Major component missing (processor/memory not seated properly) 4) Manufacturer did not include BEEP after POST in firmware, so it still could have POSTed successfully and the issue really is the monitor, 5) cable, or 6) motherboard connector.
If we get one beep, that's easy: it's either the monitor or the cable (or the connector).
If we get more than one beep, that's also easy: obviously POST did not complete successfully, but now we can work out the issue (# of beeps = errorcode) quite easily with trivial research. Troubleshooting is fantastically difficult without verbosity.
After all this hardware stuff completes is where the OS takes over. While POST completes almost immediately, obviously OS takes a lot longer.
This post-BOOT sound can be much higher quality and more detailed than the simple MIDI sounds of a motherboard speaker, so while this sound has been used for branding purposes as others have already mentioned, its primary function is to indicate that it has finished booting. (As others' answers have already mentioned.)
Thus, the Welcome Sounds enhance the end-user's experience, for it indicates BOOT has completed and they can return from making coffee now.
Side Note: It depends on how old you are if you'll notice, that nowadays POST is obfuscated in favor of a manufacturer's logo, and it completes so quick on modern hardware you wouldn't see much anyway. The beep either happens so instantaneously (right after you press the power button) that you either don't notice it, or manufacturers have started disabling it by default. Both are options you can most probably turn back on in BIOS.
Edit: It's not even BIOS we use anymore, now it's called UEFI. I'm not even 30 and my old is showing.
Asides from old systems and their delay times at start, or branding considerations (both correct reasons), one reason that I might add is that it serves as a Sensory Cue.
This is true both for blind or impaired vision users, in which startup sound is of paramount importance (this sound is the only indication they have in order to know that the system is "ready to go") as well as "regular" users with no disabilities. In this regard, there are thousands of studies about sensory cues as start points that prepare the brain for a task.
Try to picture this (or even better, test if you have the means): simply think of yourself waiting for the system to start, then you hear the sound. Is your mood the same?
If you want, try doing this very simple experiment (we already did it!): simply call some people, maybe even your fellow co-workers or family, and film them from the point they press the
ON button on a computer, until they hear the sound. 5-10 testers will be enough for this simple experiment. If your results are similar to ours, you'll see a very perceptible change on the testers. They will usually smile, or they will change their body position, or they will look more alert. Anyways, no matter the attitude they take, the important part is that most users (if not all) will react in some way
Note: New technologies will rely on aural(auditory)-haptic cues rather than only aural cues, so this answer is more related to desktop or laptop devices
Of course there are other reasons to include it, like letting the user know the hardware is working, start up is finished and they can interact with the computer, etc. but it is an extremely powerful branding tool. It is familiar, it becomes expected, and if it's a good one, it can evoke strong feelings in us (see for instance http://gizmodo.com/end-of-an-era-goodbye-mac-startup-sound-1788383059 ). It reminds us of our relationship with the computer.
Although I'm sure things are much more advanced now, my Grandfather who was blind used the POST beeps in tandem the Windows opening noises (especially once 95 released) to let him know that his speech card had not caused the system to hang. I'm not sure if it was an issue with the brand of cards he would purchase, the retailer, or just the technology wasn't mature enough yet at he time but often his various speech cards (he went through a lot) would cause either a flat no POST beep (the single letting him know it was OK) and hang the system, or get up to Windows, and once there, the card would conflict with the Windows audio itself sometimes.
I just thought I'd toss in my personal experience with having a family member that always had me calling up places asking questions about the cards, and if it wasn't for the entire fanfare at startup (POST speaker beep, Windows blasting out, etc), he would have been completely at a loss as to there being any problem whatsoever. Clearly this is isolated to his particular disability, but, just hearing Windows startup cleanly and not get garbled, let him know at least it was getting to the desktop, which followed the speech card to start it's incredibly verbose description of where he was tabbed onto. I can't clearly say for sure whether or not Microsoft had this implemented with the thought of it ever being used in such a way past say having a brand 'tone' so to speak, but, it was the bread and butter for getting the PC going for my Grandfather.
Also, I wish I could have provided a better term than 'speech card', but that's what he always called them, and they were quite hefty chunks of PCB that I believed actually used the ISA slot on his motherboard. Apologies on that sparse detail!
It's about saying Hello
The start-up sound was a machine, designed and made by people, announcing its variant of "Hello", indicating it's now present, here, and in being on, is a being, here.
By which I mean to say it's antiquated. A greeting of the past. Just as beeps and blips indicating errors in boot are now a thing of the past, the welcoming chime of a computer turning on is done.
This is most clearly felt and understood when it's removed.
This is the reason it's a big deal the new Apple Macbook Pro has turned it off.
Now we are obliged to announce our presence, and issue requests:
The cloud, longer battery life and our awareness of most computing devices being a surveillance assistant for our perceptions of the powers-that-be have ruined the romance. Our love affair with computing is over. Big Data is our new overlord.
It is a notification that the software and hardware checks have passed (with no beep codes), and that the user is now able to access an operating system through a command interface shell or an associated GUI (Graphical User Interface) desktop.
Depends on what you mean by the startup, do you mean when you actually log in? Or do you mean when you turn the computer on, once you get to the login screen the noises made serve to do nothing at all and are just branding?
When you actually turn on the computer it can make a variety of noises most commonly heard are beeps, depending on the motherboard each beep be it single double triple etc.. or long drawn out "solid" pings so to speak are typically intended to alert the user to an issue such as a malfunction on the board its self or the failure of hardware; HDDs, GPUs, CPUs, unfortunately, more people are unaware of this than those that aren't which means these noises typically go ignored and if one happens to be an alert tone for a malfunction the issue only gets worse down the line.
At least for computers, beeps are a way to inform the user of problems if there is no (connection to the) screen.
Different mainboard brands have different beeps: Mainboard debug sounds so that a technician has a hint on where to start his search if the system is not booting.
There are different ways an OS uses to give feedback to the user aside from visual. In the case of desktop devices, sound is used to give feedback and communicate something happened or to call for the attention of the user.
As @MattObee states in his answer, a start-up sound tells the user that the system turned on and thus is responsive. Other sound notifications can be used when an error happened or some process finished. The same happens when the system is turned off.
In the case of Mobile devices the sound feedback can be substituted with haptic feedback.
Part of the reason at least would be a way to notify the user that their sound system is working (or not working in the case of absence).
I can imagine how irritating it would be to have to wait for the entire PC to boot properly to test the sound was working!
I can speak to one particular UX detail where the sounds were indeed meaningful. On older macs, if there were errors which prevented booting up, the mac would present an icon (such as a disk with a question mark on it) indicating what went wrong.
However, sometimes things to so unbearably wrong that the mac couldn't even initialize the graphics card. On moments such as these, the mac would start up not with its usual "hello" sound, but would instead emit "death chimes."
These sounds were typically chosen for intuitive effect. From experience, when a Macintosh LC emits death chimes, you know instantly that your day is not going to go well.
To function-check the audio system as early as possible.
Specifically, to verify that the hardware resources in use by the sound card were not also assigned to other devices, such as a disk controller, serial port, or printer port. Specifically, base port address, IRQ channel, and DMA channel.
When a shop assembled a PC from off-the-shelf parts, it had to be careful what they mixed and matched. You generally could use almost any combination you wanted, provided you paid close attention when configuring the options above. At the time, this was done with mechanical "jumpers", or "short-pins"-- "short" in the electrical sense of tying two wires together.
If one of these jumpers fell off the pins it was supposed to short-- not uncommon after cross-country shipping, especially if the jumper was on upside-down-- the configuration of these options could change. The drive controller and the sound card might wind up on the same IRQ, and if that happened, the computer could very well corrupt data when trying to play audio (or vice-versa).
So, testing the audio hardware as early as possible was strongly desirable-- but sound cards were still add-on cards, not stock parts. The BIOS of the computer couldn't even see them, let alone talk to them, so the operating system had to boot first, and load drivers for the card, before a test sound could play.
Here's the practical result (in those days):
Customer calls in and says the system hangs. Tech asks if the system makes it through BIOS boot. Customer says yes. Tech asks if Windows makes it to the login screen. Customer says yes. Tech asks if user can log in. Customer says no, system hangs at the desktop before any icons are displayed. Tech asks if Windows plays the test sound. Customer says no. Tech tells customer how to reboot into DOS. Customer reboots into DOS. Tech tells customer to use "sbplay" to play a test file to the Sound Blaster card. Customer says system hangs. Tech tells customer to power down system, pull sound card, and reboot. Customer powers down system, removes Sound Blaster, reboots. Customer reports he can successfully log into and use Windows. Tech tells customer to check IRQ settings on all peripherals and sound card, return for service if no conflict found.
Without it, the system might very well hang at the first thing the customer did that went "click", which could be anything. "System hangs when I log out" was sometimes caused by this, for example-- some offices would disable every sound except the shutdown sound, and that's when the problem would show up, if present.
Whatever you stick in your box, app, or vehicle, TEST IT ON STARTUP whenever possible.