The Science of Sound: How Waves Shape What We Hear

Designing with Sound: Principles for Better Audio in Products

Purpose and goals

• Clarity: audio should convey information reliably (notifications, status, alerts).
• Pleasure: sound should be pleasant and fit brand personality.
• Functionality: support usability, accessibility, and feedback without annoyance.

Key principles

• Hierarchy: prioritize signals so important sounds are louder, shorter, and more distinct.
• Consistency: use consistent timbres and patterns so users learn meanings quickly.
• Simplicity: reduce unnecessary layers; concise tones communicate faster than complex sequences.
• Context-awareness: adjust volume, frequency content, or disable sounds based on environment (e.g., quiet mode, headphone detection).
• Accessibility: provide alternatives (visual, haptic) and design sounds that are distinguishable by pitch and rhythm for users with hearing differences.
• Non-intrusiveness: avoid startling frequencies or sudden loudness; employ gentle attack/decay and appropriate durations.
• Brand alignment: craft sonic identity (short motifs, instrument choices) that reflect product values without fatigue.
• Technical optimization: ensure sounds compress well, have consistent loudness (LUFS), and avoid clipping; use EQ to fit in crowded frequency ranges.

Design process

1. Define use cases and user environments.
2. Map sound events to priorities and required attributes (duration, frequency, loudness).
3. Create sketches (sine, noise, sampled elements) and iterate rapidly.
4. Test in real contexts and with diverse users, including those with hearing loss.
5. Measure perceived loudness and recognition rates; refine.
6. Implement adaptive rules (volume leveling, do-not-disturb integration).
7. Maintain an asset library with metadata (intent, LUFS, context).

Sound types & when to use them

• Alarms/alerts: short, attention-grabbing, distinct patterns.
• Notifications: subtle, brief, lower bandwidth.
• System feedback: confirmatory clicks or swishes for actions; unobtrusive.
• Transitions/ambience: gentle textures for onboarding or background that don’t compete with primary audio.

Practical tips

• Use 3–4 tones maximum for core interactions to avoid confusion.
• Target -16 to -14 LUFS for short UX sounds; normalize assets for consistent perceived loudness.
• Prefer harmonic content for pleasantness; use inharmonic/noise for urgency.
• Test on cheap speakers and headphones to ensure intelligibility.
• Provide user controls: volume, mute, and granular sound settings.

Checklist before release

• Functional mapping complete and prioritized.
• Accessibility alternatives implemented.
• Loudness normalized and mastered.
• Contextual rules and user controls tested.
• Brand sonic identity applied sparingly.

Further reading (suggested topics)

• Psychoacoustics basics, LUFS loudness measurement, sound branding, accessible audio design.