1 / 22

A Peripheral Display Toolkit

A Peripheral Display Toolkit. Tara Matthews[1] , Tye Rattenbury[1] , Scott Carter[1] , Anind K. Dey[2] , Jennifer Mankoff[1]. [1] EECS Department UC Berkeley [2] Intel-Berkeley Research Lab. UIST 2003. OUTLINE. INTRODUCTION SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION ARCHITECTURE

Download Presentation

A Peripheral Display Toolkit

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A Peripheral Display Toolkit Tara Matthews[1] , Tye Rattenbury[1] , Scott Carter[1] , Anind K. Dey[2] , Jennifer Mankoff[1] [1] EECS Department UC Berkeley [2] Intel-Berkeley Research Lab UIST 2003

  2. OUTLINE • INTRODUCTION • SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION • ARCHITECTURE • SUPPORT FOR THREE KEY CHARACTERISTICS • EXAMPLE APPLICATIONS • CONCLUSIONS AND FUTURE WORK

  3. INTRODUCTION (1/4) • Traditionally, computer interfaces have been confined to task-focused, desktop computing activities. • Ubiquitous computing devices are meant to integrate seamlessly into the world and almost disappear. • Toolkit : Peripheral displays → Ubiquitous computing devices that give information to a user without demanding their full attention.

  4. ●Physical ● Audible ● Simply displayed on a monitor ● Direct interaction occurs rarely INTRODUCTION (2/4) What does a typical peripheral display look like?

  5. INTRODUCTION (3/4) • It is difficult to build such a display for several reasons. → First, they are often physically-based and distributed. → Second, the key characteristics of peripheral displays must be dealt with in an ad-hoc manner. • We believe there is a need for tools supporting the creation of peripheral displays.

  6. INTRODUCTION (4/4) • They have designed and implemented the Peripheral Displays Toolkit (PTK). → Providing architectural support for key features of peripheral displays. → Allowing designers to more easily prototype them and supporting reuse of code. • Architecture adds support for three key characteristics of peripheral displays: 1) Abstraction 2) Notification 3) Transitions

  7. SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION (1/5) A. What is attention? (1/2) 1) Categorize attention into four main zones: preattention, inattention, divided attention, and focused attention.

  8. SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION (2/5) A. What is attention? (2/2) 2) Peripheral displays are displays that show information that a person is aware of, but not focused on. →This includes inattention and divided attention, but not pre-attention or focused attention. 3) Ambient displays rely on divided attention. 4) Alerting displays, such as our bus arrival display, also rely on divided attention.

  9. Ignore Change blind Make Aware Interrupt Demand action Inattention Divided attention Focused attention No attention SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION (3/5) B. Characteristics of Peripheral Displays (1/3) • Notification levels: 1) Notification • Demand action • Interrupt • Make aware • Change blind • Ignore

  10. SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION (4/5) B. Characteristics of Peripheral Displays (2/3) • Transitions are based upon the notification level of the data, and themodality of the display. • Alerting displays typically utilize abrupt transitions for important information. • Several applications have shown that significant changes in the interface will draw a user’s attention. 2) Transitions

  11. SURVEY OF PERIPHERAL DISPLAYS AND ATTENTION (5/5) B. Characteristics of Peripheral Displays (2/3) • Abstraction is the process of removing or extracting data so that the result includes fewer or different details than the original. • Types of abstraction: 1. Degradation 2. Feature extraction 3) Abstraction

  12. 1 2 3 4 ARCHITECTURE

  13. SUPPORT FOR THREE KEY CHARACTERISTICS (1/3) A) Abstraction • We currently provide default abstractors that convert from input data to numbers, switches, audio, images, light, and motors. • Application-specific feature abstraction is specified by overriding a Translate class and passing that in to the appropriate abstractor.

  14. SUPPORT FOR THREE KEY CHARACTERISTICS (2/3) B) Notification • Notification levels are commonly chosen based on : • Thresholds • Exact match • Degree of change • Pattern matching

  15. SUPPORT FOR THREE KEY CHARACTERISTICS (3/3) C) Transitions • A transition’s primary role is to create a series of display events for the output object that provide a desired change of awareness for the user. • Our default transition class supports the major types of transitions found in our survey: • Smooth transitions • Abrupt transitions • Attention grabbing transitions

  16. EXAMPLE APPLICATIONS (1/5) A) Bus Mobile • Giving users a sense of how much time is left until popular buses reach their chosen bus stops. • It rises one inch every minute until it disappears under the skirt when the bus has left the bus stop. • Problem: The Bus Mobile did not properly use notification.

  17. EXAMPLE APPLICATIONS (2/5) B) Bus LED • The display consists of six columns of LED lights, labeled below with the corresponding bus number. • When the bus is six minutes away, the LED lights flash on and off a few times to catch the user’s attention. • Using a different abstractor to translate minutes to number of LED lights and changes to the parameters for the notification setters.

  18. EXAMPLE APPLICATIONS (3/5) C) Stock-News Displays • Our stock and news ticker supports arbitrary notification levels and transitions. • Change-blind transitions were implemented as fade-out/fade-in transitions. • Make-aware transitions were implemented as a single flash. • Interrupttransitions were implemented as multiple flashes.

  19. EXAMPLE APPLICATIONS (4/5) D) Remote audio awareness — Ring Ticker • The Ring Ticker is designed for those who cannot easily hear important audio events. • When the phone rings, the word “ring!” slowly fades into view as it scrolls across the ticker. • This display demonstrates feature abstraction. • Notification level is always set to either “make aware” or “ignore”.

  20. EXAMPLE APPLICATIONS (5/5) D) Remote audio awareness —Guitar • The Guitar, provides awareness of audio events occurring in a remote space by plucking a string. • It used an abstractor to convert remote audio volumes to servomotor positions. • Notification levels were set to change blind, make aware, or interrupt, using a threshold setter, based on volume.

  21. CONCLUSIONS AND FUTURE WORK (1/2) • Three key characteristics of peripheral displays: abstraction, notification, and transitions. • We developed a tool to support the building of peripheral displays, based on these characteristics. • In the future, we plan to conduct studies that can help us to determine how best to populate our library.

  22. CONCLUSIONS AND FUTURE WORK (2/2) • We will expand the range of animations supported by our transition implementation, and include more sophisticated support for animation in our transition class. • We are also interested in expanding the interpretation of local context currently available to transition classes in the toolkit.

More Related