Skip to main content
ExodeUI

EXODEUI DESKTOP

A little space for good ideas.

Choose your platform to get the official ExodeUI installer.

Looking for Intel Mac or other builds? Explore the web studio or check all download options.

Prefer the browser? Try for free in your browser →
UX1 min read·Updated November 2026·By the ExodeUI team

UI Sound Design: When Interface Sounds Help and When They Annoy

How to design UI sounds: which interactions deserve sound, how to keep sounds short and consistent, browser autoplay rules, accessibility and pairing sound with motion.

Direct Summary & Definition

Core Takeaway

UI sounds help when they confirm an important action, signal something people might miss, or add character to a moment that matters. Keep them short, quiet and consistent, never make sound the only signal, give people a way to turn sounds off, and respect device silent modes and browser autoplay rules. Sync sounds with the motion they accompany.

Which interactions deserve sound

Material Design's sound guidance describes UI sounds as a way to communicate, express brand and add delight, and warns against overuse. A practical filter:

  • Yes: payment sent, message sent, timer finished, recording started, errors in hands-busy contexts
  • Maybe: celebrations, game-like progress, first-run moments
  • No: every tap, hover, scroll or keystroke

Short, quiet and consistent

Most UI sounds should be well under a second. Make them a family: shared tone, similar loudness, related pitches for related actions, such as rising for success and falling for cancel. Mix them quieter than media playback, because people hear them many times a day.

Platform and browser rules

Apple's Human Interface Guidelines ask apps to respect the user's audio settings and the silent switch. Browsers block audio that plays before the user has interacted with the page, as MDN's autoplay guide explains, so web UI sounds should start only in response to a user action and handle a blocked play attempt gracefully.

Accessibility and control

Never make sound the only way information is given: pair it with a visual change. Offer a setting to turn UI sounds off, and remember people using screen readers already hear a lot of audio. Avoid loud or sudden sounds, and keep sounds for errors calm rather than alarming.

Pairing sound with motion

Sound and motion feel connected when they line up: the click on contact, the whoosh as the panel moves, the chime as the check mark completes. Trigger sounds from animation events rather than separate timers so they stay in sync when timings change.

Building this in ExodeUI

ExodeUI, which we make, components fire events your code listens for, such as pressed or completed. Play your sound from those events and it stays in sync with the motion even after someone retunes a spring. Sound itself stays in your app, where you can respect mute settings and browser autoplay rules.

Key Principles to Remember

  • Use sound for important confirmations and hard-to-see events
  • Keep sounds short, quiet and consistent as a family
  • Start sounds only after user interaction on the web
  • Always pair sound with a visual change and offer an off switch
  • Trigger sounds from animation events to keep them in sync

Frequently Asked Questions

Sources

  1. About sound — Material Design
  2. Playing audio — Apple Human Interface Guidelines
  3. Autoplay guide for media and Web Audio APIs — MDN Web Docs

Related Guides & Examples

Motion with events

Open an interactive component that reports events, a natural place to hook in sound.

Open the send button
Try for free