Give a sound a job

An interface sound can mark a deliberate action or lend a digital object a sense of material character. A brief click might suggest a mechanical control; a softer tone might accompany a gentle transition.

Before considering its character, ask what the sound contributes. Is it helping someone understand an action, supporting an experience centered on listening, or simply filling a silence? The answer changes how prominent it should be.

Consider the listening environment

The same sound can be welcome in private and intrusive in a shared room. Headphones, existing music, volume settings, and device controls all form part of the experience. An application cannot assume that it has someone's entire soundscape to itself.

Optional sound effects deserve clear controls. A person should be able to understand what they are silencing, particularly when background music and short interaction sounds serve different purposes.

Make silence usable

Someone may not hear a cue because audio is muted, the environment is noisy, or their hearing differs. Essential information needs another understandable expression, such as visible text or a change that assistive technology can identify.

Thinking about the silent version can clarify the purpose of the audible one. Sound then becomes a considered addition to an experience that already communicates its meaning.

Further reading: Apple's guidance on playing audio.