A useful UI sound marks an event the interface has actually completed. In a prototype, distinguish a button press from the work that follows it. A bright completion chime on the first tap can tell a listener a file is saved while a progress indicator is still moving.
Map the state change before describing the sound
Take a fictional packing-list app. A designer needs a short product demo that shows adding an item, undoing it and completing the list. Give each sound one job.
| Event | Visual evidence | Draft sound direction |
|---|---|---|
| Item added | A new row appears | A soft, dry tap with a rounded attack |
| Undo succeeds | The row disappears | A short downward pair of soft notes |
| Entire list completed | The complete state appears | Two resolved tones with a clean tail |
Try the sequence with sound muted first. Can a tester tell whether the row was added? Repair the visual state if necessary. Sound can reinforce it for listeners who enable audio.
Generate and audition one family
In Oakgen Sound Effects, describe the first cue as “One short, rounded wooden tap, close and dry, like a small block touched with a felt tip. Quiet tail.” For undo, keep the material and space while changing the contour. A different instrument for every interaction can make three cues sound as if they belong to three apps.
Trim leading silence in an audio editor and align the sound to the frame where the state changes. Use markers for “tap,” “row appears” and “completed” in a screen-recorded demo. A tool such as Audacity can label these points without changing the sound itself. Audacity label tracks
Test the annoying case
A user may add eight items in a row. Repeat the add cue eight times at the speed of a quick tapper. If the tails overlap or the pattern becomes distracting, shorten the tail, reduce the level or reserve the cue for the final confirmation. Keep the finished-list sound for that one transition.
Finally, show a teammate the same demo with cues A and B at similar loudness. Ask when they thought the save had succeeded. If the answer moves to the initial tap, shift or remove the misleading cue. Save the approved mapping, event names and audio files together so a new screen can reuse the same sound language next sprint.
Make the first interaction cue
Start with one short sound for a state change your users can see.
Frequently asked questions
Which prototype interactions deserve sound?
Choose events where a listener needs to distinguish a change of state. Test the design silently first, then keep a cue only when it clarifies that change.
How can I compare two interface sounds fairly?
Use the same interaction recording, match their perceived loudness and change only the candidate cue. Ask listeners what action they think occurred.
Does generating the sounds add them to my prototype?
Generate the clips in Oakgen, then bind or edit them into the prototype using your design or demo tool. Check playback in the environment where the demo will run.



