platform-guideline 1 linked patterns checked
Android Developers: Add haptic feedback to events
Documents Android haptic feedback APIs, predefined constants, view.performHapticFeedback, vibrator APIs, user-setting behavior, hardware support, and event-specific haptic implementation.
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 platform haptic APIs, predefined constants, user settings, and hardware support. |
Comparisons supported by this source
- Haptic feedback vs touch gesture vs toast notification vs error state vs confirmation dialog vs progress bar
Supports event-specific haptic APIs, predefined constants, hardware support, and user settings.
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: .