A correct ding should read instantly, end quickly, and avoid frequencies that feel sharp on phones. Use the library when you need a ready-made one-shot, or prompt new takes when you must match a brand tone, device speaker, or animation speed.
Decide the intent: confirm vs reward
Confirmation dings should be short and neutral, while reward dings can be brighter or two-note. If your UI already has lots of click sounds, aim for a smoother transient so it does not sound like another tap.
- For confirmation: single tone, short decay, minimal sparkle
- For reward: slightly higher pitch or two-note up interval
- Avoid long rings that overlap with the next UI event
Control attack and tail in the prompt
The fastest way to make a ding feel modern is a tight envelope: a crisp onset with a clean cutoff. If the ding feels harsh, reduce brightness or ask for a softer attack rather than adding reverb.
- Ask for a "clean transient" or "rounded attack" depending on style
- Specify "short decay" or "tight tail" to stop masking speech
- Call out "no reverb" or "minimal room tone" for app UX
Choose stereo width for the playback device
Many dings will be heard on mono phone speakers. A narrow or centered ding stays consistent across devices, while moderate stereo width can feel premium in videos or desktop apps.
- Mono or narrow stereo for mobile and notifications
- Moderate width for desktop UI videos and screen recordings
- Avoid extreme width that disappears when summed to mono
Match loudness and avoid ear fatigue
Success cues repeat often. Keep the perceived loudness comfortable and avoid piercing high peaks that become annoying after dozens of correct answers.
- Prefer balanced highs over sharp, needle-like pings
- Filter excessive low-end so it does not thump on small speakers
- If it feels aggressive, lower brightness and shorten the tail
