Tools

Filters

General Purpose ⓘ

Meta-information about the tool.

Year Rangeⓘ

The year a tool was first publicly released or discussed in an academic paper.

Start Year

End Year

Platforms (∧)ⓘ

The OS or software framework needed to run the tool.

Unknown

Windows

macOS

Linux

Unity

Rust

Android

iOS

Web

iPad

Java

Python

Faust

Blender

STM32

C++

Processing

Pebble

HDAPI

Pure Data

Raspberry Pi

Protools and Max/MSP

Electron

libmapper

NodeJS

Availability (∨)ⓘ

If the tool can be obtained by the public.

Available

Unavailable

Licenses (∨)ⓘ

Tye type of license applied to the tool.

Unknown

Open Source

Proprietary

Non-Commercial Research Use Only

Venue (∨)ⓘ

The venue(s) for publications.

Intended Use Case (∨)ⓘ

The primary purposes for which the tool was developed.

Accessibility

Collaboration

Communication

Education

Gaming

Haptic Augmentation

Hardware Control

Music

Notifications

Prototyping

Psychophysics

Simulation

Virtual Reality

Hardware Control ⓘ

Aspects of the tool related to supported haptic hardware.

Haptic Category (∨)ⓘ

The general types of haptic output devices controlled by the tool.

Vibrotactile

Skin Stretch/Compression

Force Feedback

Temperature

Electrotactile

Hardware Abstractions (∨)ⓘ

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.

Bespoke

Consumer

Class

None

Device Names (∨)ⓘ

The hardware supported by the tool. This may be incomplete.

Body Position (∨)ⓘ

Parts of the body where stimuli are felt, if the tool explicitly shows this.

Arm

Foot

Hand

Head

Leg

N/A

Tongue

Torso

Interaction and Interface ⓘ

Aspects of the tool related to the creation of haptic effects.

Driving Feature (∧)ⓘ

If haptic content is controlled over time, by other actions, or both.

Time

Action

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.

Target-centric

Device-centric

Location-aware

Media Support (∨)ⓘ

Support for non-haptic media in the workspace, even if just to aid in manual synchronization.

None

Audio

Visual

Olfactory

Iterative Playback (∨)ⓘ

If haptic effects can be played back from the tool to aid in the design process.

Yes

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

Library

Sequencing

Description

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.

Dataflow

Demonstration

Generic Menu

Keyframe

N/A

Score

Track

Storage (∨)ⓘ

How data is stored for import/export or internally to the software.

AIFF

CSV

Collada