Android API

Tool Summary

General Purpose Information
Year of First Releaseⓘ The year a tool was first publicly released or discussed in an academic paper.	2008
Platformⓘ The OS or software framework needed to run the tool.	Android
Availabilityⓘ If the tool can be obtained by the public.	Available
Licenseⓘ Tye type of license applied to the tool.	Open Source (Apache 2.0)
Venueⓘ The venue(s) for publications.	N/A
Intended Use Caseⓘ The primary purposes for which the tool was developed.	Haptic Augmentation

Hardware Control Information
Haptic Categoryⓘ The general types of haptic output devices controlled by the tool.	Vibrotactile
Hardware Abstractionⓘ How broad the type of hardware support is for a tool. Bespoke: Hardware is custom built, including open hardware. Consumer: Support is limited to a specific commercial device or a family of devices. Class: Any device with the same affordances can be used, possibly with some configuration required.	Consumer
Device Namesⓘ The hardware supported by the tool. This may be incomplete.	Android
Body Positionⓘ Parts of the body where stimuli are felt, if the tool explicitly shows this.	N/A

Interaction and Interface Information
Driving Featureⓘ If haptic content is controlled over time, by other actions, or both.	Time
Effect Localizationⓘ How the desired location of stimuli is mapped to the device. Device-centric: No spatial information is taken into acccount. Actuators are directly controlled. Target-centric: Stimuli are placed on the body or are assigned to a virtual object to be triggered through interaction. The tool handles how the device will display the effect. Location-aware: The desired location of an effect is taken into account to some extent, but is ultimately presented in context of the output device.	Device-centric
Media Supportⓘ Support for non-haptic media in the workspace, even if just to aid in manual synchronization.	None
Iterative Playbackⓘ If haptic effects can be played back from the tool to aid in the design process.	N/A
Design Approachesⓘ Broadly, the methods available to create a desired effect. Direct parametric control (DPC): low-level parameters are directly modifiable. Process: parameters are controllable by an abstract process. Sequencing: reusable effects are ordered in time to create complex effects. Library: a library of pre-existing effects is available for use or re-use. Description: a natural language description of the experience is used to find an appropriate effect, often through searching a library.	DPC, Process, Sequencing, Library
Interaction Metaphorsⓘ Common UI metaphors that define how a user interacts with a tool. Track: a timeline represents an interactive channel containing effects. Keyframe: key points of the effect are set and behavior between them is interpolated. Score: an adaptation of a musical score or notation represents haptic effects. Dataflow: a dataflow programming model is used to control haptic output. Demonstration: physical actions or other data are mapped simply to effects or parameters. Generic Menu: typical GUI elements (e.g., sliders) are used to control effects with the absence of other metaphors.	N/A
Storageⓘ How data is stored for import/export or internally to the software.	None
Connectivityⓘ How the tool can be extended to support new data, devices, and software.	API

Additional Information

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.

For more information, consult the Android API documentation and Android Open Source Project (AOSP).