Battle of the beeps | the usability of sound

dublin-bus-versus-the-luas

I recently bought a 10-journey ticket for Dublin bus. When I swiped the card at the reader, it emitted a beep.

Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

This is one Dublin bus beep

This beep suggests an error.

So I looked closely at the reader, where the display was very faint. I could just make out ‘9 journeys left.’ I looked at the driver for approval and he nodded as if to say, no problem, go on.

Now compare that to the LUAS. The LUAS smartcard is similar to a Dublin bus ticket. When you swipe at the reader, it too emits a beep.

Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.

These are several LUAS beeps during morning rush hour

This beep suggests success, rather than failure.

Why?

At its simplest, it’s the length of the beep. A success beep should be short, and in turn, an error longer. The Dublin bus beep is more than a second long and is insistent, suggesting that you need to take action.

The LUAS beep is short, suggesting all is fine and you go on your way.

It is subtle, but it makes all the difference. An ominous beep slows people down; they will take a moment to realise everything is fine and they can board the bus. That makes a big difference during rush hour.

Any Dublin bus users out there think this is a problem?

Thanks to my colleague John Wood for twitter research on this subject.

Categories Spotted, Usability