Best practices
When to use haptics
We recommend to use haptic feedback in these scenarios:
- Action Confirmation - when users perform an important action, a subtle vibration confirms that the action was received and processed.
- Notifications & Alerts - when an event needs the user’s attention, distinct haptic patterns make sure the user notices, even if sound or visuals are missed.
- Error Prevention & Feedback -when users make mistakes, haptics can signal the error instantly, preventing further issues.
- Navigation & Guidance - when guiding users through multi-step tasks or transitions, haptics reinforce progress and help keep them on track.
- Accessibility Support - when designing for users with visual or hearing impairments, haptic feedback provides an alternative tactile channel for understanding actions, alerts, and system states.
- Delight & Engagement - when enhancing user experience, subtle haptic effects can make the app feel more interactive and engaging.
- Error Prevention & Feedback - when users make mistakes, haptics can signal the error instantly, preventing further issues.
- Navigation & Guidance - when guiding users through multi-step tasks or transitions, haptics reinforce progress and help keep them on track.
- Accessibility Support - when designing for users with visual or hearing impairments, haptic feedback provides an alternative tactile channel for understanding actions, alerts, and system states.
- Delight & Engagement - when enhancing user experience, subtle haptic effects can make the app feel more interactive and engaging.
When NOT to use haptics
Avoid haptic feedback in these scenarios:
- Frequent interactions like typing or continuous scrolling (use very subtle feedback only).
- Background processes that don't require user attention.
- Decorative purposes without functional benefit.
What should be avoided
- Overuse: Too frequent haptic feedback becomes annoying and loses effectiveness.
- Inconsistent patterns: Using different haptics for the same actions confuses users.
- Unpleasant sensations: Effects that feel "off" or are too strong for the context.
- Lag: Delayed haptic feedback breaks the cause-and-effect relationship.
- Ignoring system settings: Not respecting user preferences or accessibility settings.
- Standalone reliance: Using haptics as the only feedback mechanism without visual/audio alternatives.
Additional guidelines
- Test extensively: Haptic experiences vary significantly across devices and user preferences.
- Synchronize with visual/audio: Ensure all feedback types trigger simultaneously for cohesive experience.
- Use system defaults: Leverage platform-standard haptic patterns for familiar interactions.
- Design for all scenarios: Consider how haptics affect other device functions and contexts.