1 / 17

Exploring the Design and Use of Messaging and Situated Displays

Exploring the Design and Use of Messaging and Situated Displays. Keith Cheverst and Dan Fitton Lancaster University. Exploring Messaging to Public/Private Places Rather than people! Issues Patterns of use Interactions that do (or do not) occur Meeting dependability requirements

abram
Télécharger la présentation

Exploring the Design and Use of Messaging and Situated Displays

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. Exploring the Design and Use of Messaging and Situated Displays Keith Cheverst and Dan Fitton Lancaster University

  2. Exploring Messaging to Public/Private Places Rather than people! Issues Patterns of use Interactions that do (or do not) occur Meeting dependability requirements 2 Case studies HERMES Computing Department of Lancaster University SPAM Support for Care staff in distributed offices Talk Overview…

  3. Case Study 1 HERMES: Exploring messaging with situated displays in Lancaster’s Computing Department

  4. HERMES… • Motivation… • Paranoia about missing that appointment and not being able to let anybody know in time!! • “Sorry running 40 minutes late today”

  5. Contrasting with Post-it Notes… • Control of various dimensions • Visibility/Privacy… • Who can leave public messages • Who can remove messages • Security • Remote Interaction… • Leaving & Reading, Owner & Other • SMS (MMS…), Web portals… • Appropriation…

  6. Initial Design Constraints… • Had to Utilise LV • Disabilities legislation • Easy to deploy • Self contained • Doesn’t require running PC • Wireless Communications • Information Appliance • Case Design… • Dependability • We hate iButtons !

  7. Development and Patterns of use… • Phased development.. • Participatory Design… • Initially only access through the web portal… • Required users to authenticate • Too heavy weight… • Difficult to remember URL • Introduced e-mail for receiving messages, • Will be introducing instant messaging support, e.g. msn messenger.

  8. Patterns of use… • Initially only a single ‘public’ message… • Users found cost of changing too high • Consequently messages were being left on display… • Introduced Temporary & Default messages • Will be enabling users to clear temporary message on device itself and to select messages. • “I usually remember to stick up a post-it note only after locking the door behind me”

  9. Current Plans… • Use of Context • Back in ten minutes, countdown, etc. • Using time etc. to determine most likely temp message • Explore how users trade-off security & ease-of-use • Need more convenient authentication… • Return to exploring use of private messages. • Explore further remote interaction dimension • Enabling others to view displayed messages remotely, e.g. via the doorplate owner’s home page… • Possible Additional Coordination Role…, is Alan in today? • Increase user’s likelihood of updating their doorplate? • Sharing personal context… • Enabling others to leave messages remotely, after authentication?.

  10. Case Study 2: Situated displays to support staff across geographically remote offices …

  11. Requirements Capture… Remote Staff and Residents Phone Phone E-mail Phone One/two members of Staff in Office at Location B One member of Staff in Office at Location A

  12. Workshop – (Dec, 2001) • Discussed problems, • e.g. demand for phone • Demonstrated HERMES… • Staff felt that similar messaging system would be useful • Reduce burden on phone • Provide lightweight asynchronous communication channel

  13. The SPAM Solution… Low noise, Compact, No space invaders! Extensive testing…

  14. The SPAM solution… Remote Staff and Residents Phone Phone SMS SMS E-mail Phone SPAM One/two members of Staff in Office at Location B One member of Staff in Office at Location A

  15. User Reaction… • Initial comments • We're delighted with it .. we've all started to use it very quickly .. and we're using it a lot • ..I think people at first thought it was going to be really complicated but it couldn't be easier .. .. we find it extraordinarily useful..

  16. Broad Categories of use… • Use as Confirmation • Has Fax, email got through? • Has x left yet? • General coordination between sites… • e.g. Ordering food! • Use to signify delays/need for help, • Related to phone use, usually requests for phone to become free. • "please ring car wont start so cannot take ph and sm to cc barbara". • Coordination with mobile users • e.g. "Pizza & and chips are ready come on in :-)" • Remote requests • e.g. request to test the fire alarm • Some jokes and general chit-chat etc. • Developing Language and Use

  17. Concluding Remarks… • Messaging to places rather than people • Novel interaction paradigm ? • cf work by McCarthy: Outcast etc. • …certainly little work looking at use of this class of system over constant and long periods of use • Such periods of use are required before users are likely to develop new usages… • Initially messaging solutions need to fit in with existing patterns of use

More Related