Your phone made dozens of sounds today and almost none of them were chosen by the brands that triggered them. The payment confirmation, the message sent, the task completed: mostly iOS and Android defaults. Apple and Google picked those sounds, and they are doing brand work on behalf of whoever happens to be on screen.
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. Individually they're tiny, a fraction of a second each, but they're some of the most frequently heard sounds a brand produces, often played hundreds or thousands of times per user per month. A 30 second ad runs once; a notification chime runs every day, for years.
Why most companies skip it
Visual UX has a mature discipline behind it, design systems, component libraries, accessibility standards. Audio UX rarely gets the same treatment, partly because it's not visible in a screenshot or a Figma file, and partly because most product teams don't have anyone whose job is specifically sound. Which leaves the category 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. A confirmation chime should sound like it belongs to the same brand as your TV ad or sonic logo, built from the same melodic and tonal DNA, not picked from a generic sound effects library.
Design for repetition. A sound a user hears once a year can be bold. A sound they hear fifty times a day needs to be short, low fatigue, and pleasant on the fiftieth listen, not just the first.
Design for context. Notification sounds get heard in quiet rooms, noisy commutes, and silent mode vibrations. Good UX sound design accounts for the realistic range of listening environments, not just a studio monitor.
Document it. A short UX sound guideline, which tone for which action, volume and length conventions, dos and don'ts, keeps every future feature release consistent, the same way a component library keeps visual design consistent.
Which sounds does a product actually make?
Most teams underestimate how many there are. This is the inventory we work through during 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?
Shorter than you think. A half-second confirmation tone feels too short on the first listen and exactly right on the fiftieth. That is the correct yardstick: design for the fiftieth time, not for the presentation.
There is a practical floor. Below roughly 150 milliseconds a listener no longer hears a tone but a click, and the sound loses its brand character. Between that 150 milliseconds and around two seconds sits almost everything usable.
What goes wrong if you leave the system sounds in place?
Two things, and the second is the expensive one.
The first is obvious: your brand sounds like every other brand. That default iOS tone is also what someone hears from their bank, their delivery service and their calendar app.
The second is subtler. System sounds are designed to fit the operating system, not your brand. If your TV commercial is warm and acoustic and your app makes a crisp digital ping, those two work against each other. The user does not consciously notice, but the recognition you build with the campaign is chipped away a little on every app session.
How do you test UX sound?
Not on a studio monitor. Our order:
- Phone speaker, held at eye level. The most common listening situation and the hardest test, because the low end disappears entirely.
- 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 it disappears there, it is too subtle.
- Fifty times in a row. The only way to hear whether something will start to grate.
Almost everyone skips that last step, and it is the one that decides whether a sound is still switched on a year later or whether users have turned their notifications off.
Where it fits into a bigger sonic identity
UX sound rarely stands alone, it's one layer of a complete sonic branding & music strategy, alongside a sonic logo and brand anthem, all composed together so a user recognises the brand whether they're watching an ad or unlocking the app. If your product makes sounds nobody designed on purpose, that's usually the easiest place to start fixing it. Curious what that would look like for your product? Check our FAQ or get in touch.