download.zip
- A fixed take someone else chose — pitch, length, character
- A license to re-check on every rebrand
- A file to host, cache, and keep in sync with design changes
- Retuning it means finding a different file
blip
three ways to get
a ui sound effect.
Type it, download it, or shape it — a click, a toggle, or an alert can come from three different places, and the choice shapes what you ship: a file to host and re-license, or a few lines of code that need nothing at all.
- 3 approaches compared
- 0 kb with a recipe
- 3 platforms, one recipe
roomywarmsharpdry
comparea file, a prompt,
a file, a prompt,
or a recipe.
All three can produce a click that sounds fine on the first listen. The difference shows up later, once you need to change it.
regenerate('click')
- Still hands you an audio file to host, same as a library
- Retuning means wording the prompt again and hoping
- Quality and voice can vary between takes, even from one prompt
- Licensing terms differ by tool — worth reading before shipping
playClick()
- Shaped by ear with faders, not re-prompted and hoped for
- Exports as code — nothing to host, cache, or re-download
- Half a tone brighter is a number, not a new take
- Yours outright, with no license to track
why does the source matter, not just the sound?
Every option above can produce something that sounds right today. The difference shows up later — when the interaction needs to be a few milliseconds shorter, when a file needs re-hosting after a rebrand, or when the same cue has to exist natively in a Kotlin build and a SwiftUI build without turning into two different sounds. A file locks in a decision. A synthesis recipe keeps it open — see exactly what that looks like in code.
what actually matterspick by what you
pick by what you
need next.
The right answer depends less on which sounds best today, and more on what has to happen after you have a sound you like.
shipping to more than one platform A recipe travels — a file has to be re-encoded and re-tested for each one. See the Web Audio, Swift, and Kotlin patterns.
building a set, not one sound A consistent voice across five states is easier to hold onto with one adjustable recipe than five separately sourced files. See a sound for every state.
one sound, once For a single cue with no reuse ahead, a library take or a quick prompt is a reasonable choice — this page is for when the decision needs to hold up longer than that. Why a tunable set is different →
faq
the useful details.
Is a synthesized sound always better than a recorded one?
No — a recorded or sampled sound can capture a texture synthesis does not reach easily, like real-world foley. The advantage of synthesis shows up in what happens after: nothing to host, retune, or re-license, not necessarily a better first listen.
Do AI-generated sound effects come with a license I need to check?
Usually, and terms vary by tool — some restrict commercial use, some require attribution, some change over time. Read the specific license before shipping any AI-generated or downloaded sound in a paid product.
What if I already have a sample pack I'm happy with?
Keep using it. Blip Blip is for the moments a fixed sample does not fit — a state it does not cover, a platform it was never exported for, a tweak that would mean re-downloading — not a mandatory replacement for something that already works.
Can I try the synthesis approach without committing to it?
Yes — designing and previewing a sound needs no account and no cost. Only exporting the finished code requires signing in, and the first five exports are free.
shape one.
see which you’d pick.
Open Blip Blip and compare the recipe against whatever is already in your asset folder.