🔥NOTE: The Studio library for Android is now in beta and is under development. The information on this page is therefore subject to change.
While the shift to higher-quality haptics is underway in the industry, the truth is that not all devices and brands are as far along this journey as others. As a result, there can be differences in haptic performance and functions between devices and brands as shown in this chart:
|Feature||iOS (iPhone)||Android (beta)|
|Amplitude Control||All compatible iPhones (iPhone 8 and newer) support Amplitude Control.||Some Android phones are equipped with ERM actuators which are incapable of amplitude control. Haptics created with Lofelt Studio will not work on these phones. The phone can report its ability to support Amplitude Control, so you can make any needed changes in your program when running on such a phone.|
|Frequency Control||All compatible iPhones (iPhone 8 and newer) support Frequency Control.||At the time of this writing, none of the phones running Android are equipped with actuators capable of frequency control, nor does the Vibrator API of Android support frequency control. On these phones, haptics will always play with a fixed frequency unique to the specific actuator used in the phone regardless of the frequency modulation specified in a haptic clip.|
|Emphasis Points||All compatible iPhones (iPhone 8 and newer) support Emphasis Points.||At the time of this writing, Emphasis Points in a haptic clip will be omitted during playback on Android phones.|
|Unlimited Haptic Playback Duration||All compatible iPhones (iPhone 8 and newer) can play haptics without limit when using the Studio framework for iOS.||At the time of this writing, Android phones will exhibit a maximum playback duration of a haptic clip which differs between phone makes and models. Android’s Vibration API does not provide any method for querying this maximum playback length or any means for being notified when the haptic playback is stopped. Therefore, longer haptic clips may stop playing sooner than desired on some Android phones—haptic playback will resume when you trigger the next haptic in your app.|
|Real-time audio-to-haptics||All compatible iPhones (iPhone 8 and newer) support the real-time audio-to-haptics feature of the iOS Framework.||At the time of this writing, the Vibration API of the Android OS does not provide the adequate control of the phone’s actuator required to achieve real-time audio-to-haptic conversion. This function is therefore not provided in the Studio library for Android.|