platform-guideline 1 linked patterns checked
Google Help: Get started with Voice Access spoken commands
Documents Android Voice Access for controlling a device with spoken commands, including opening apps, navigating, editing text, and hands-free use.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Voice command | Choose voice command when the interaction problem is spoken activation or control, not typed search, command browsing, key-chord acceleration, or ordinary dictation alone. | Voice capture starts only after explicit user invocation, platform voice-access command, or documented wake condition. | Supports mobile spoken commands for app control, navigation, and text editing. |
Comparisons supported by this source
- Voice command vs keyboard shortcut vs command palette vs prompt box vs text input vs touch gesture
Supports Android spoken commands for navigation, app opening, and text editing.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Google. Last checked: .