A correct cue should be instantly readable, short enough for rapid interactions, and pleasant after repeated use. When browsing or prompting, focus on transient shape (how fast it speaks), tail length (how long it lingers), and tone (bright vs warm). Use prompts that name the action (correct answer, saved, completed) and the instrument character (bell, synth ping, 8-bit) so regenerations stay consistent.
Match the moment: tap, answer, or achievement
Different correct moments need different weight. A tiny checkbox should not sound like a level clear, and a streak reward should build slightly longer than a single tap confirmation.
- For single taps, ask for a short ping with minimal decay
- For quiz answers, choose a clearer attack so it cuts through speech
- For achievements, prompt a two-step rise or small flourish
Control attack and tail to avoid fatigue
Correct sounds are often repeated. Overly sharp transients or long, bright tails can become tiring. Aim for a crisp start with a compact finish that leaves space for the next interaction.
- Use phrases like fast attack, tight decay, short tail
- If it feels harsh, prompt softer transient or warmer tone
- If it feels muddy, reduce tail and remove room reflections
Pick a tone color that fits your UI style
Tone communicates personality. A glassy bell reads clean and modern, while an 8-bit pulse reads playful. Keep the pitch range consistent so users learn the sound quickly.
- Modern UI: clean sine ping, subtle stereo width, no reverb
- Playful games: arcade chord, slight grit, quick release
- Calm learning tools: warm bell, rounded attack, gentle brightness
Avoid common mistakes in correct cues
The wrong correct sound can feel like an error, a notification, or a loud alert. Keep it unmistakably positive and easy to trim.
- Avoid long ringing tails that overlap rapid scoring
- Avoid heavy low-end that competes with music beds
- Avoid overly complex melodies for simple confirmations
