Your phone has made dozens of sounds today, and hardly any of them were picked by the brand behind them. The payment going through, the message being sent, the task marked done: mostly iOS and Android defaults. So Apple and Google chose those sounds, and they're now doing brand work for whoever happens to be on your screen (just not for you).
What UX sound design actually covers
UX sound design is the deliberate creation of the small audio moments inside a digital product: notification tones, success chimes, error states, loading sounds, onboarding flourishes, transition swooshes. Each one is tiny, a fraction of a second. But add them up and they're some of the sounds people hear most from a brand, hundreds or even thousands of times a month per user. A 30 second ad plays once. A notification chime plays every day, for years.
Why most companies skip it
Visual UX has a whole discipline behind it: design systems, component libraries, accessibility standards. Audio UX hardly ever gets that kind of love. Partly because you can't see it in a screenshot or a Figma file. Partly because most product teams simply don't have a sound person. Which means the field is still wide open. Ipsos puts sonic assets at around 8% of brand assets industry wide, despite audio outperforming visuals on recall.
Getting it right
Start from the brand, not the platform. Your confirmation chime should sound like it comes from the same family as your TV ad or sonic logo. Same melody, same sort of sound. Not something grabbed from a sound effects library.
Design for repetition. Something you hear once a year can be loud and bold. Something you hear fifty times a day can't. It has to be short, easy on the ears, and still nice the fiftieth time, not just the first.
Design for context. People hear notifications in a quiet bedroom, on a packed train to work, or only as a buzz in silent mode. Good UX sound design works in all of those places. Not just on a studio monitor.
Document it. Write a short UX sound guideline. Which tone goes with which action, how loud, how long, what's allowed and what isn't. That keeps every new feature in line, just like a component library does for the visuals.
Which sounds does a product actually make?
There are more of them than most teams think. Here's the list we go through in an audit:
| Moment | What the sound does | Target length | Most common mistake |
|---|---|---|---|
| App open | Brand recognition | 0.8–2 sec | Too long, so it gets in the way |
| Confirmation | “That worked” | 0.2–0.5 sec | Too cheerful, so it grates by the fiftieth time |
| Notification | Ask for attention without startling | 0.3–0.8 sec | Leaving the default system tone in place |
| Error | Correct without punishing | 0.2–0.4 sec | Low and ominous, making the user feel stupid |
| Transition | Give direction | 0.15–0.4 sec | Audible as a standalone sound rather than as movement |
| Task complete | Reward | 0.5–1.5 sec | The same sound as an ordinary confirmation |
Six moments, together less than five seconds of audio. That is the entire project. It is the smallest brief in sonic branding and at the same time the one that gets played most often.
How long should a UX sound be?
Probably shorter than you'd guess. A half-second confirmation tone feels too short the first time you hear it, and just right by the fiftieth time, which is the one that counts. Design for listen number fifty, not for the presentation to the board.
There is a limit, though. Go below about 150 milliseconds and people stop hearing a tone. They hear a click, and the brand character is gone. Pretty much everything useful sits between those 150 milliseconds and about two seconds.
What goes wrong if you leave the system sounds in place?
Two things, and the second is the expensive one.
The first one's obvious. You sound like everybody else. That default iOS tone is also what people hear from their bank, their delivery app and their calendar.
The second one is sneakier, and I think more expensive. System sounds are made to fit the operating system, not your brand, so if your TV commercial is warm and acoustic while your app goes "ping" in crisp digital, the two are quietly working against each other. Nobody consciously notices that, but every single time somebody opens the app a little of the recognition your campaign built up gets chipped away again.
How do you test UX sound?
Not on a studio monitor. Our order:
- Phone speaker, held at eye level. This is how most people hear it, and it's the toughest test, because all the bass is gone.
- Cheap earbuds. Not the expensive reference headphones. Whatever most people actually have in.
- In a room with background noise. A café, a train, an open-plan office. If you lose it there, it's too subtle.
- Fifty times in a row. Honestly the only way to find out if it'll start to annoy you.
Almost nobody does that last one. Yet it's exactly what decides whether your sound is still on a year from now, or whether people have muted your notifications.
Where it fits into a bigger sonic identity
UX sound rarely stands alone. It's one layer of a complete sonic branding & music strategy, next to a sonic logo and a brand anthem, and ideally we write all of it together so people recognise you whether they're watching an ad or unlocking the app. If your product makes sounds that nobody ever designed on purpose, that's usually the easiest place to start. Wondering what that could sound like for your product? Check our FAQ or get in touch.
Two more places your brand makes sound every day: your podcast intro, and the office, where your employees hear your brand more than customers do.