Sound design rules for casual mobile games: no gunshots in a word game
Sound is the part of a small game that's easiest to get wrong and hardest to notice you've got wrong. You test with the volume down, or on a laptop, and everything seems fine. Then you play on a phone with headphones and the game is shouting at you.
Over a few games I threw out a lot of sounds. These are the rules that came out of it.
What I threw out
- In Wordhoard, the word-strike sound was basically a gunshot. Satisfying in an action game, absurd in a word game set in a medieval manuscript.
- The same game's page turn was a burst of hissing white noise. Its replacement, a harp, sounded nothing like a page turning.
- A letter tap that played twice, once on press and again on release.
- Backpack Battle's first sound set: generic arcade clips at full volume, picked by file name. A fantasy fight that sounded like a slot machine.
- In Emberfall, noise-based drums that turned harsh after Bluetooth compression.
The rules
1. No raw noise bursts. White noise at full volume is the harshest sound you can make. If a sound needs noise (a swish, a rustle), ease it in over about 20 ms, filter it, and keep it quiet.
2. Hits are knocks and stamps, not booms. Wordhoard's strike became a seal stamp: a wooden knock and a soft paper pat. Backpack Battle's blade hits are a swing and a soft thunk. Weight comes from timing and pitch, not volume.
3. If it imitates something real, it must sound like that thing, or be a recording of it. A synthesised page turn never sounds like a page. A CC0 recording of a real page does, and costs nothing. Backpack Battle now uses 37 CC0 foley recordings: leather creak on pick-up, leather thud on drop, a bow release with an arrow whistle, a muted shield thud.
4. One sound per action. A tap makes one sound. A drag starts its sound once it actually moves. A sound on both press and release reads as a glitch.
5. Pick sounds against a written brief, with limits. For each action, write down how it should feel ("soft, warm, short, lower than the music"). Then choose sounds by measurement as well as by ear: loudness, brightness (spectral centroid) and attack time. Never by file name alone.
6. Mix quietly. Backpack Battle runs a master volume around 0.45, music at about 0.22, a 9 kHz low-pass to take the fizz off, and small random pitch changes so repeated sounds don't grate. Emberfall's music defaults to 30%.
7. Test on a phone with headphones. Bluetooth headphones compress audio and go to sleep in silence, clipping the next sound when they wake. Emberfall keeps the link alive with an inaudible tone while music plays. Nothing on a laptop speaker tells you that.
8. Silence the engine when nothing plays. A Web Audio context that never suspends keeps the phone awake. That was one of the battery problems. Suspend it after 30 quiet seconds, not sooner, or the next tap's sound plays late.
Where the sounds come from
Almost everything is CC0 (public domain): foley libraries, Kenney's sound packs (Wordhoard's page turns are two alternating recordings of a real book) and recorded music. That means no licences to track and no attribution problems.
Win and loss
Win and loss sounds deserve special care, because they play at the most emotional moment. Backpack Battle went from a blaring fanfare to a short harp arpeggio for a win and cello pizzicato for a loss. A loss sound should be gentle. The player already feels bad, and the game doesn't need to rub it in.