platform-guideline 1 linked patterns checked
Android Developers: Haptics design principles
Documents Android haptics design principles, using haptics to enrich direct manipulation and events, avoiding overuse, respecting user settings, and matching effect strength to interaction meaning.
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 |
|---|---|---|---|
| Haptic feedback | Choose haptic feedback when the tactile effect reinforces a visible interaction milestone and improves physical confidence without carrying required information alone. | A haptic effect plays only for a user-relevant interaction event and stays synchronized with the visible state change it reinforces. | Supports semantic strength, intentional timing, direct manipulation, and overuse constraints. |
Comparisons supported by this source
- Haptic feedback vs touch gesture vs toast notification vs error state vs confirmation dialog vs progress bar
Supports matching haptic strength and timing to interaction meaning while avoiding overuse.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Android Developers. Last checked: .