|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.
|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.
|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, Sequencing, Library|
| Interaction Metaphorsⓘ |
Common UI metaphors that define how a user interacts with a tool.
Feel Messenger is a haptically augmented text messaging application structured around families of “feel effects”. Feel widgets or “feelgits” are types of effects that can be varied by a set of parameters, or “feelbits”. These parameters are made available to users of Feel Messenger through a set of menus. New effects can also be created by playing pre-existing effects one after the other.
For more information, consult the CHI’15 WIP paper.