1 / 19

Amarino:a toolkit for the rapid prototyping of mobile ubiquitous computing

MobileHCI '10. Amarino:a toolkit for the rapid prototyping of mobile ubiquitous computing. Bonifaz Kaufmann and Leah Buechley MIT Media Lab High-Low Tech Group Cambridge, MA 02139, USA bonifaz@mit.edu, leah@media.mit.edu.

maris
Download Presentation

Amarino:a toolkit for the rapid prototyping of mobile ubiquitous computing

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. MobileHCI '10 Amarino:atoolkit for the rapid prototyping of mobile ubiquitous computing Bonifaz Kaufmann and Leah Buechley MIT Media Lab High-Low Tech Group Cambridge, MA 02139, USA bonifaz@mit.edu, leah@media.mit.edu Proceedings of the 12th international conference on Human computer interaction with mobile devices and services

  2. OUTLINE • INTRODUCTION • RELATED RESEARCH • APPROACH • AMARINO • Android Interface • Architecture • MeetAndroidLibrary • Using Amarino to Create Custom Android Applications • Documentation • AMARINO EXAMPLES • Multicolor lamp • CallMyShirt • Workout • EVALUATION • CONCLUSION AND FUTURE WORK

  3. INTRODUCTION • “Even the most powerful notebook computer, with access to a worldwide information network, still focuses attention on a single box” – Mark Weiser • Smart phone ““boxes”” engross and isolate us with their power to capture our attention. • Problem: negative social and physical consequences • Solution: ambient and tangible interfaces (Tangible bits)

  4. INTRODUCTION • Motive: tangibles are difficult to design and construct. Ambient interfaces to smart phones are especially rare, perhaps because they are particularly challenging to build. • Goal: Amarino aims to facilitate the development of tangible interfaces to smart phones by eliminating several of the developments steps that are required to build them.

  5. RELATED RESEARCH • WeWrite (IDC '09) • United-Pulse (MobileHCI '08) • eye-q (MobileHCI '06) • NEAT-o-Games (CIE '08) • MobSens (Pervasive '09)

  6. APPROACH • Different kinds of expertise(skill) • Developing smart phone applications • Implementing communication protocols • Building tangible devices • Standardized communication protocol • Additional goals for our project • Easy to use • Extendible • Open source

  7. AMARINO Amarino MeetAndroid

  8. AMARINO - Android Interface

  9. All built-in events in Amarino

  10. AMARINO - Architecture

  11. AMARINO - MeetAndroid Library

  12. AMARINO - Using Amarino to Create Custom Android Applications

  13. AMARINO - Documentation

  14. AMARINO EXAMPLES Multicolor lamp CallMyShirt Workout

  15. EVALUATION • one day workshop for a group of 13 engineering and design students, 10 male and 3 female. All were in their 20s or 30s. • + our group included undergraduate, masters, and PhD students. Total: 15. • 12 had previous Arduino programming experience and 5 had previous Android programming experience.

  16. EVALUATION • All students were able to complete the online tutorial successfully within 45 minutes. • the students were asked to experiment with Amarino’’s inbuilt events. Most students successfully used the compass or accelerometer events to change the intensity of an LED. • The third challenge was to write a simple Android application. • an Android interface with a single button that was used to switch an Arduino-connected LED on and off.

  17. EVALUATION • One student wrote a program that activated the phone’’s vibration motor whenever a light sensor attached to the Arduino was covered with the hand. • The most compelling example however was from a student who used the Android’’s built-in speech recognition engine to build a voice-activated light.

  18. CONCLUSION AND FUTURE WORK • Developers work easily with more of the artifacts in our environments——from phones to furniture to clothing. • We focused on keeping our tools easy to use. • novices easily extendible • useful for experts

  19. CONCLUSION AND FUTURE WORK • provide users with access to higher level events, like gestures and spoken words for example. • add support for communication via wireless LAN——this functionality could be particularly useful in the home environment. • investigate a location detection feature that would automatically activate particular event collections based on current location.

More Related