A Mac voice app should not display listening when microphone access is denied. Explain the blocked capability, preserve the user's intended task, and provide a deliberate route to retry after access changes.
Keep recording permission separate from transcription and text-insertion capability. Fixing microphone access does not prove the app can recognise speech or place text into the target field.
Check capture capability before starting a session
Review Apple's current media-authorisation guidance for native setup and permission handling. Validate the actual app target and supported macOS environment rather than assuming a development run represents the distributed build.
Model not-yet-requested, granted, denied, and other relevant outcomes under the API contract. Ask in the context of a recording action with a clear explanation of why access is needed.
Test a fictional bug-report dictation
A user focuses a test editor and starts recording a harmless bug report. Test first request accepted, first request denied, later permission granted, later permission revoked, and repeated shortcut presses while permission is unresolved.
The app should create at most the intended session, avoid capturing before authorisation, and keep the target state clear. After a settings change, require a supported fresh action or refresh path rather than silently beginning to record from an old request.
Test an unavailable input device separately. Permission granted with no usable microphone is a different condition from denial and needs a different explanation.
Preserve privacy and useful recovery
Show a blocked state that does not imply audio was captured. Avoid logging dictated text or broad device information merely to diagnose permission. A safe session reference and capability category can support routine investigation.
If the user cancels while visiting settings, invalidate the original recording intent. A later permission grant must not revive a cancelled session or insert text unexpectedly.
The tradeoff is convenient onboarding versus user control. Requesting access immediately at launch can simplify setup while asking before the user understands the feature. A contextual request can be clearer, provided the blocked path remains understandable.
The Mac dictation workflow guide discusses the wider capture-to-insertion sequence. StackSpeech appears in the portfolio as a Mac voice-input project with hold-or-toggle capture and safe cancellation. This permission matrix is proposed guidance and claims no completed device test or universal compatibility.
Questions about microphone denial
Should denial trigger repeated system prompts?
Follow the current native permission behaviour and offer an appropriate settings route where needed. Repeating a request that cannot succeed is confusing.
Does a granted microphone permission authorise insertion?
No. Treat capture, recognition, and interaction with another application's text field as distinct capabilities.
What should a review test first?
Deny access, cancel the task, grant access later, and verify no old recording starts. Bring unexpected capture to a Mac voice-workflow review.