A microphone indicator should reflect what the app is actually doing, not merely that a shortcut was pressed. Users need to distinguish active capture from permission failure, processing after capture, and a session that has been cancelled.
Use one authoritative session model for the menu bar, overlay, and main window. Independent indicators can disagree and make users unsure whether audio is still being collected.
Define states by established capability
Include idle, starting, listening, stopping, processing, review, cancelled, and failed where the product requires them. Show a blocked capability without implying capture began.
Review Apple's NSStatusItem documentation for the native surface and media-authorisation guidance for capture setup. The app still owns the relationship between those APIs and its visible state.
Test a fictional menu-bar dictation session
Use a harmless sentence and start capture from another application's field. Verify the listening state appears only after the supported capture boundary is established and changes when capture stops, even if recognition remains pending.
Test permission denial, no input device, disconnected microphone, repeated shortcut, cancellation, app sleep, and a delayed recognition result. Inspect menu label, icon, overlay, audio state, and final insertion eligibility together.
No device or accessibility result is claimed in this proposed matrix. Record supported macOS and app versions and use controlled fixtures rather than private dictated content.
Keep feedback accessible and nonintrusive
Use understandable text or accessible descriptions alongside colour and animation. Provide a clear stop or cancel route. A decorative pulsing icon alone may not explain whether the microphone is active or the transcript is being processed.
Status UI should avoid becoming the text destination accidentally. Test mouse interaction, keyboard focus, preview acceptance, and return to the original app under the explicit insertion policy.
The tradeoff is persistent visibility versus interruption. A small menu-bar indicator can be unobtrusive but easy to miss; a larger overlay can communicate state while disrupting focus. Evaluate both capture confidence and task continuity with representative users.
Keep error details out of the public indicator while offering a safe reference and specific next action. The user needs to know whether to grant permission, select a device, retry, or review saved text.
The Mac workflow guide covers these boundaries. StackSpeech's portfolio entry documents a live listening indicator. This state matrix is proposed guidance, not a measured reliability claim.
Questions about microphone indicators
Should processing use the same listening state?
No, when capture has ended. Distinguish microphone activity from recognition or cleanup so users understand the data-collection boundary.
Can icon colour be the only signal?
Use additional understandable and accessible meaning. Test the actual assistive and visual conditions of the supported audience.
What should a review inspect first?
Compare visible state with actual capture through denial, stop, cancel, and delayed completion. Bring disagreements to a Mac capture-state review.