The Android haptics subsystem refers to hardware and software features that contribute to the creation of stimuli through the sense of touch. Creating haptic effects requires a high degree of hardware dependencies, while perceiving haptic stimuli requires a high degree of user dependencies and preferences. This dichotomy challenges device manufacturers to develop and maximize haptic user benefits in the Android ecosystem.
This page describes the compliance instructions for device manufacturers and app developers, and provides clear guidance on the best use of the Android haptics APIs. The topic is split into three sections:
A step-by-step checklist detailing haptic SW and HW compliance
The checklist walks you through the key elements of the hardware configuration process.
An in-depth look at UX and design principles
These principles illustrate the importance of hardware compliance in improving the haptics UX for Android end users.
A foundation for haptic framework
This lists the set of UX principles that Android haptic improvements are driven by.
To learn more about compatibility in general, read the Android Compatibility Definition Document.
To learn more about using haptics in Android, read the Android Developer Documentation.