Haptics

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.

Implementing haptic effects correctly requires up-to-date, compatible hardware. For users to properly perceive haptic stimuli, specific preferences must be tweaked to create the desired effects. Manufacturers must satisfy both requirements to properly implement haptics on Android.

The following guides describe the compliance instructions for device manufacturers and app developers, and provides clear guidance on the best use of the Android haptics APIs:

• A step-by-step checklist detailing haptic SW and HW compliance

  The checklist walks you through the key elements of the hardware configuration process.

• A foundation for haptic framework

  This lists the set of UX principles that Android haptic improvements are driven by.

• 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.

• Assess hardware

  Learn how to assess the haptic effects implementation with the necessary test equipment and apply your findings to the performance map to draw conclusions about the performance of your device under test.

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.