CHI 2014: Cross-Device Interaction

Smarties: An Input System for Wall Display Development by Oliver Chapuis

  • wall display input issues: mouse/keyboard – stuck to desk; touch – too close; laser pointer, air gesture, hard to track; prefer mobile tablet
  • input programming is complex and expensive; provide a system for easy and fast prototyping; mobile device(s) -> protocol -> library -> wall
  • interface: multiple pucks representing “cursors” at multiple locations on the wall; each puck has functions of a mouse with multi-touch and other functions like text; collaborative; you have your own pucks and share control; store and retrieve pucks
  • protocol and libraries: multi-client event based; synchronization for shared pucks; C++, Java, JavaScript; similar to mouse management but applied to each puck
  • applications: attach pucks to wall lenses for exploration of map
  • software available

Conductor: Enabling and Understanding Cross-Device Interaction by Peter Hamilton

  • vision: the move from physical desk to mobile device has lost some of the utility of large physical desk space; interactions across multiple devices by one user; “symphony” of devices
  • ***** Conductor: targeted transmissions to other devices; cue broadcasting; minimally invasive; contextual actions; persistent connections -> duet functional bonding;'duet management; cross-application views; peripheral device sharing (eg share a Bluetooth keyboard); cross-device task manager
  • user study: large search and integration task given a whiteboard, paper and pen, 5 Nexus 10 and 5 Nexus 7 devices; all used the devices; using spacial memory to store specific pieces of data on individuals devices

Panelrama: Enabling Easy Specification of Cross-Device Web Applications by Jishuo Yang

  • by 2017 the average household will have 4 internet enabled devices; how to take advantage of those
  • automatically reassign UI elements to the available devices based on best device for certain functions (example uses laptop/projector = slide, phone = remote control, pebble watch = presentation time, google glass = presenter notes)
  • panel: UI building block; group of UI components with a shared purpose
  • Panelrama: attributes – scorn size, proximity to user, keyboard, touchscreen; developers score each characteristic for each panel – extensible attributes; Panelerama models attributes of devices; optimize layout across multiple devies for each panel; minimize code changes, just define panel tag and panel definition
  • developer study: 8 developers converted single device apps to multi-device in 40 minutes or less
  • code available soon

Interactive Development of Cross-Device User Interfaces by Michael Nebeling

  • meeting room scenario: parts of UI distributed to speaker tablet, projector, and audience phones; device-centric with different roles
  • classroom scenario: teacher's device and 3 student groups; role centric ie student + group or teacher
  • design time: device types including unknown devices; user roles; adapt UI elements: adapt UI across devices; design and testing; reuse
  • run-time requirements: dynamic integration of devices, update the distribution, matching and adaptation
  • XDStudio: GUI builder for multi-device UI; “DUI” = distributed user interface; on device and simulated authoring modes; user study validated that different modes are preferred for different situations; define distribution profiles for devices, device classes, and roles; client-server architecture
  • evaluation: would people use authoring modes? used the scenarios with mix of mode availability; device-centric scenario benefits more from both modes, where classroom was fine with simulation
This entry was posted in Interaction Design. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *