What it is
Short two-oscillator envelopes generated in the browser: no audio files, no licensing. Info gets a soft tick that is normally never played, action gets a ~250ms rising chime, critical gets a distinct double pulse. At most one chime per arrival batch, at the batch's highest severity.
Also called: notification sound · alert tone · ding · audio alert
See it
How it works
- 1Browsers keep audio suspended until a gesture, so one capture-phase pointerdown/keydown listener resumes the context once and then detaches.
- 2Events arriving before that unlock show their toast without sound — 'we never queue/blast retroactive audio'.
- 3The unlock installer resets its own flag on detach so a remount can re-install rather than losing the listener forever.
Why we built it
Synthesis avoids assets and licensing entirely. The one-chime-per-batch rule exists so a burst does not become sound spam, and info is silent by design so routine events never make noise.
The problem
- Undifferentiated alert sounds
- Retroactive audio blasts after a tab wake
Sound familiar?
What you get
You can tell urgency by ear
Never more than one sound per batch
What's inside
Exactly one audible path per alert
Visible tab gets the in-page chime; hidden tab with a desktop notification lets the OS carry the alert; hidden tab without one still chimes, so nothing is silent by accident.
Mute and do-not-disturb
A one-tap speaker toggle plus timed do-not-disturb windows, with the panel stating when the quiet ends and the mute lifting itself when it expires.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →