UX Sound Design

Create functional and emotionally resonant audio for digital products using Audio UX methodology—from notification sounds to complete sonic systems.

When to Use This Skill

• Designing notification sounds for an app
• Creating a complete audio system for a digital product
• Adding audio feedback to UI interactions
• Building accessible audio cues
• Defining audio guidelines for product teams
• Evaluating and improving existing product sounds

Methodology Foundation

Source: Audio UX + Design Thinking Principles

Core Principle: "Audio UX is the strategic and intentional use of sound to enhance the user experience." Unlike music or entertainment audio, UX sound design serves a function first. The best product sounds are invisible when working correctly and noticeable only when something needs attention.

Why This Matters: Sound is the most underutilized tool in digital product design. Research shows audio feedback improves task completion, reduces errors, and creates stronger brand associations. Yet most products either ignore sound entirely or use generic, forgettable audio.

What Claude Does vs What You Decide

What This Skill Does

1. Designs functional audio cues - Sounds that communicate status, confirmation, and errors
2. Creates emotional connections - Audio that reinforces brand personality
3. Builds audio systems - Coherent families of related sounds
4. Ensures accessibility - Audio for users with visual impairments
5. Documents audio guidelines - Specifications for consistent implementation

How to Use

Design Product Sounds

Help me design audio for [product/feature].
Interaction: [what the user does]
Feedback needed: [what the sound should communicate]
Brand personality: [tone/feeling]

Create Audio System

Create an audio system for [app/product].
Key interactions: [list]
Brand: [personality traits]
Constraints: [technical limitations]

Review Existing Audio

Review these product sounds for UX effectiveness:
[describe current sounds]
Issues: [problems you've noticed]

Instructions

When designing UX sounds, follow this methodology:

Step 1: Understand the Function Categories

Every product sound serves one of these purposes.

## UX Sound Categories

### 1. FEEDBACK SOUNDS
Confirm that an action was registered.

| Type | Purpose | Example |
|------|---------|---------|
| Confirmation | Action completed | Send button click |
| Progress | Something is happening | Upload progress |
| Success | Task finished successfully | Payment confirmed |
| Error | Something went wrong | Form validation error |
| Warning | Attention needed | Low battery |

### 2. NOTIFICATION SOUNDS
Alert user to external events.

| Type | Purpose | Example |
|------|---------|---------|
| Alert | Immediate attention | New message |
| Reminder | Scheduled prompt | Calendar event |
| Update | Information available | Download complete |
| Social | Human interaction | Someone liked your post |

### 3. NAVIGATION SOUNDS
Spatial orientation and movement.

| Type | Purpose | Example |
|------|---------|---------|
| Transition | Moving between views | Screen change |
| Selection | Choosing an option | Menu item hover |
| Boundary | End of scrollable content | List bottom reached |

### 4. AMBIENT/BACKGROUND
Context and mood.

| Type | Purpose | Example |
|------|---------|---------|
| Presence | App is running | Subtle background tone |
| Mode | Current state | Focus mode active |
| Celebration | Achievement | Goal reached |

Step 2: Apply Design Principles

Core principles for effective UX audio.

## UX Sound Design Principles

### 1. FUNCTION FIRST
- Sound must communicate something useful
- Ask: "What information does this convey?"
- If no clear function, consider no sound

### 2. DISTINCT BUT RELATED
- Each sound should be recognizably different
- All sounds should feel like a family
- Use consistent:
  - Tonal palette (key/scale)
  - Timbral characteristics
  - Duration ranges
  - Dynamic levels

### 3. APPROPRIATE URGENCY
- Match sound urgency to message urgency
- Error ≠ always alarming
- Success ≠ always celebratory
- Scale:
  1. Subtle acknowledgment
  2. Gentle notification
  3. Attention-getting alert
  4. Urgent alarm

### 4. CONTEXT AWARE
- Consider when/where users hear this
- Public spaces: shorter, more subtle
- Private: can be more expressive
- Frequency: often-heard sounds must be less intrusive

### 5. ACCESSIBLE
- Don't rely solely on sound
- Always pair with visual feedback
- Consider frequency range (avoid only high frequencies)
- Ensure distinctiveness for users who can't see visual cues

### 6. CONTROLLABLE
- Users must be able to mute/adjust
- Provide volume controls
- Respect system settings
- Never surprise with unexpected sound

Step 3: Create the Sound Palette

Define the raw materials for your audio system.

## Sound Palette Development

### Step 3.1: Define Brand Sound Attributes

Translate brand personality into audio terms:

| Brand Attribute | Sound Translation |
|-----------------|-------------------|
| Playful | Bouncy, melodic, varied pitch |
| Professional | Clean, precise, consonant |
| Innovative | Modern synthesis, unique timbres |
| Warm | Rounded, organic, mid-range |
| Energetic | Fast attack, bright, rhythmic |
| Calm | Soft attack, slow decay, filtered |

### Step 3.2: Choose Your Palette Elements

**Tonal Center**
- Pick a key (e.g., C major, F major)
- All sounds should relate to this key
- Create harmonic cohesion

**Timbre Family**
- Acoustic (piano, bells, wood)
- Synthetic (sine, FM, wavetable)
- Hybrid (processed acoustic)
- Choose based on brand

**Duration Range**
- Micro: 50-150ms (feedback)
- Short: 150-500ms (notifications)
- Medium: 500-1500ms (transitions)
- Long: 1500ms+ (celebrations)

**Dynamic Range**
- Define min/max volume levels
- Relative loudness between sound types
- Error > Notification > Feedback (typically)

### Step 3.3: Document the Palette

```markdown
## [Product] Sound Palette

**Tonal Center**: F major
**Character**: Warm, professional, approachable

**Primary Timbre**: Rounded sine with subtle harmonics
**Secondary Timbre**: Soft mallet (marimba-like)
**Accent Timbre**: Clean bell tone

**Durations**:
- Feedback: 80-120ms
- Notification: 200-400ms
- Transition: 300-600ms
- Celebration: 800-1500ms

**Loudness Hierarchy** (relative to baseline):
1. Alerts: +3dB
2. Notifications: 0dB (baseline)
3. Feedback: -6dB
4. Ambient: -12dB

---

### Step 4: Design Individual Sounds

Process for creating each sound.

Sound Design Process

For Each Sound:

1. Define the Function

• What exactly does this communicate?
• What action triggered it?
• What should user understand?

2. Determine Urgency Level

• 1 (subtle) → 5 (urgent)
• This affects: loudness, duration, pitch, complexity

3. Consider Context

• How often is it heard?
• Where is user when hearing it?
• What's user's emotional state?

4. Design Parameters

5. Create Variations

• Design 3-5 options
• Test in context
• Get user feedback
• Iterate

Common Patterns

Confirmation/Success:

• Rising pitch (positive)
• Clean, resolved harmony
• Quick, satisfying
• Example: Two notes ascending a third

Error/Warning:

• Falling or dissonant
• More complex/harsh
• Attention-getting