platform-guideline 1 linked patterns checked
MDN Web Docs: Vibration API
Documents limited web vibration support, device vibration hardware access, Navigator.vibrate, single pulses, vibration and pause patterns, cancellation with zero or empty patterns, and no-op behavior on unsupported devices.
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 web vibration support limits, pulse patterns, cancellation, and unsupported-device behavior. |
Comparisons supported by this source
- Haptic feedback vs touch gesture vs toast notification vs error state vs confirmation dialog vs progress bar
Supports web vibration availability, pulse patterns, cancellation, and no-op behavior on unsupported devices.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: MDN Web Docs. Last checked: .