Secondary UX sounds are played less frequently in a UI. They should reflect a product’s personality, but they are primarily used for functional purposes, to inform users of state changes, or to indicate infrequent actions.

- A subtle tone can express when a content feed is refreshed
- https://kstatic.googleusercontent.com/files/957287f6c429b75995d4afa8057350cebd8d25fa6bfd0df56c56169a51282869e45d0c11200071381209194f131e00e60487469e96bb5a1b5407c1fe69bb020a
- A tone can inform users when something isn't available for interaction
- https://kstatic.googleusercontent.com/files/c6a6a69bb8c84e7df3041f9b1b4b0ebcc1588be75f72d6970c6fe48d456cd95df2e5799a806951fc7b4d0058e8579c3a06ed96154eee738d126e1bae05394353

University of Michigan - Ann Arbor

- Primary UX sounds
- Usage
- Secondary UX sounds

System sounds

Material Design Documentation

Primary UX sounds are generated by an operating system (or device) to provide user feedback. They can add sound to any interaction, such as:

- Menu navigation
- Confirming a user’s direct action
- Data input

They should be in harmony with a product’s sound aesthetic, while remaining simple and understated.

Primary UX sounds

These sounds occur more frequently than other sounds in the UI. Because they are repeated throughout an experience, they should be suitable for being played often (without feeling annoying or redundant).

- Navigation example
- Selection example

Learn Before

Related