Capture state must be visible and the indicator must not be disableable
Aliases: privacy LED · recording indicator · hardware mute
What it is
Once a microphone sends audio to recognition or upload, capture state must be visible to the room, and that indicator must not be turn-off-able in software. Visibility serves people in the room—including the owner—in judging whether recording is happening now. It is not there so the speaker can set level. A hardware mute cuts the path; a lamp or OS-level dot asserts state. Together they keep capture from being hidden.
Why it happens
A voice pipeline is acoustically covert: no shutter click, no visible buffer. If the indicator lives only in app UI, the app can omit it, draw it on another display, or cover it in fullscreen. A system- or hardware-level lamp or mandatory status icon takes drawing rights away from the app; changing the skin cannot kill it. An indicator that can be switched off is no indicator: malware or a buggy app will switch it off. Always-on keyword spotting is not the same state as “audio is being sent to recognition”; the indicator should be stronger for the latter and at least honest in hardware or settings for the former. A waveform is different: it tells the speaker that sound reached the mic. A privacy indicator tells everyone that the pipe is open.
Studying it
Walk every capture path: post-wake listening, in-app dictation, background hotword, accessory mics. Record which layer owns the indicator, whether settings can disable it, and whether it survives fullscreen and a dark display. User research asks whether a bystander and the owner can tell from two metres that capture is on, not whether the speaker likes the chrome. Make “indicator off” an experimental condition and count how many people still detect capture.
Where it stops holding
Purely on-chip keyword spotting that never leaves the device often faces a weaker legal and product demand than cloud recognition, but the always-on microphone still has to be stated on the box and in settings. An OS recording dot is not replaced by a second, disableable lamp the app draws. Hearing aids and walkie-talkies have their own physical conventions. A visible indicator does not mean content is not uploaded; it answers “do we know capture is on,” not “what was captured.”
Applying it
- Put the capture indicator at system or hardware layer; app settings must not offer “turn off the recording lamp.”
- Hardware mute must cut the microphone path and move the indicator into an explicit not-capturing state, rather than leaving the lamp on while software claims it is not listening.
- Accept in fullscreen games, with the display off, and with audio playing on an external speaker: once capture starts, people in the room must still be able to discover the indicator.