|General Purpose Information|
| Year of First Releaseⓘ |
The year a tool was first publicly released or discussed in an academic paper.
| Platformⓘ |
The OS or software framework needed to run the tool.
| Availabilityⓘ |
If the tool can be obtained by the public.
| Licenseⓘ |
Tye type of license applied to the tool.
|Open Source (Apache 2.0)|
|Hardware Control Information|
| Haptic Categoryⓘ |
The general types of haptic output devices controlled by the tool.
| Hardware Abstractionⓘ |
How broad the type of hardware support is for a tool.
|Consumer (Android Devices)|
|Interaction and Interface Information|
| Driving Featureⓘ |
If haptic content is controlled over time, by other actions, or both.
| Effect Localizationⓘ |
How the desired location of stimuli is mapped to the device.
| Media Supportⓘ |
Support for non-haptic media in the workspace, even if just to aid in manual synchronization.
| Iterative Playbackⓘ |
If haptic effects can be played back from the tool to aid in the design process.
| Design Approachesⓘ |
Broadly, the methods available to create a desired effect.
|DPC, Process, Sequencing, Library|
| Interaction Metaphorsⓘ |
Common UI metaphors that define how a user interacts with a tool.
The Android API consists of preset
VibrationEffect assets and developer-added compositions of the “click” and “tick” effects. Waveforms can also be created by specifying periods a sequence of vibration durations or durations and associated amplitudes. Audio-coupled effects can also be generated using the
HapticGenerator. There are significant differences in hardware and software support across different Android devices and OS versions, including basic features such as amplitude control.