Limits...
ECCE Toolkit: Prototyping Sensor-Based Interaction

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.


Screenshot of the interface for configuring cross-device behaviors. (a) A direct mapping: The button on port I2 (see Figure 3) is used to toggle the visibility of a label on the graphical interface of a tablet; (b) A trigger-action: If I am at more than 10 cm from the distance sensor change the background of the projected display to “red”.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f006: Screenshot of the interface for configuring cross-device behaviors. (a) A direct mapping: The button on port I2 (see Figure 3) is used to toggle the visibility of a label on the graphical interface of a tablet; (b) A trigger-action: If I am at more than 10 cm from the distance sensor change the background of the projected display to “red”.

Mentions: The previous tool provides a coherent definition of all the objects in the ecosystem in terms of their components and attributes. The Couplings Editor exploits these descriptions to link components using rules that manage the interplay between physical and digital components. Again, a graphical interface is provided for the end-user configurability of behaviors (Figure 6). ECCE has been developed to allow a wide range of integration of physical and digital components following an event-driven approach. At this stage of development, cross-device behaviors can be implemented with two sensors/actuators couplings:


ECCE Toolkit: Prototyping Sensor-Based Interaction
Screenshot of the interface for configuring cross-device behaviors. (a) A direct mapping: The button on port I2 (see Figure 3) is used to toggle the visibility of a label on the graphical interface of a tablet; (b) A trigger-action: If I am at more than 10 cm from the distance sensor change the background of the projected display to “red”.
© Copyright Policy - open-access
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC5375724&req=5

sensors-17-00438-f006: Screenshot of the interface for configuring cross-device behaviors. (a) A direct mapping: The button on port I2 (see Figure 3) is used to toggle the visibility of a label on the graphical interface of a tablet; (b) A trigger-action: If I am at more than 10 cm from the distance sensor change the background of the projected display to “red”.
Mentions: The previous tool provides a coherent definition of all the objects in the ecosystem in terms of their components and attributes. The Couplings Editor exploits these descriptions to link components using rules that manage the interplay between physical and digital components. Again, a graphical interface is provided for the end-user configurability of behaviors (Figure 6). ECCE has been developed to allow a wide range of integration of physical and digital components following an event-driven approach. At this stage of development, cross-device behaviors can be implemented with two sensors/actuators couplings:

View Article: PubMed Central - PubMed

ABSTRACT

Building and exploring physical user interfaces requires high technical skills and hours of specialized work. The behavior of multiple devices with heterogeneous input/output channels and connectivity has to be programmed in a context where not only the software interface matters, but also the hardware components are critical (e.g., sensors and actuators). Prototyping physical interaction is hindered by the challenges of: (1) programming interactions among physical sensors/actuators and digital interfaces; (2) implementing functionality for different platforms in different programming languages; and (3) building custom electronic-incorporated objects. We present ECCE (Entities, Components, Couplings and Ecosystems), a toolkit for non-programmers that copes with these issues by abstracting from low-level implementations, thus lowering the complexity of prototyping small-scale, sensor-based physical interfaces to support the design process. A user evaluation provides insights and use cases of the kind of applications that can be developed with the toolkit.

No MeSH data available.