Mobile phones became multi-purpose devices supporting their users with large variety of applications for various tasks. Not only the number of available applications is increasing, also the number of applications people are using on their devices is growing, as well as the amount of time people spent on their smartphones daily is getting bigger. In this workshop paper, we briefly describe our past work on understanding mobile application usage. We explain our research tool for measuring mobile application usage, called AppSensor, and discuss possibilities to exploit the information of mobile application usage to inform the reasoning about users’ contexts. We contribute our source code to the workshop for a discussion and prototyping of use cases leveraging the information of which application a user is currently using.
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
What's in the apps for context?
1. What’s in the Apps for Context?
Extending a Sensor for Studying App
Usage to Informing Context-awareness
Matthias Böhmer
Christian Lander
Antonio Krüger
UbiMI Workshop at UbiComp 2013
September 8-9, 2013
Zürich, Switzerland
9. Support for App Launching
9
- Adaptive launcher menu
- Support visual search for apps
- Presenting 5 icons for next app
- Implements different models
- Sequentially used apps
- Prediction model
- Locally most used apps
- Most recently used apps
- Most frequently used apps
- Application AppKicker
- Extension as a widget
- Deployed on app store
- 53,000 installations
Will be presented at
UbiComp 2013
Session „Systems“
Wed 8:30-10:00
10. App Recommender System
10
- Implementation of a recommender system
- Context-aware (location, time and previous app)
- Based on traces of application usage (AppSensor)
- Application appazaar
- Deployed on app store
- 7,200 installations
- Testbed for different recommender engines
11. Findings
- Interruptions do not happen as often as expected
- 8% of app use is interrupted by app switching
- 3% of app use is interrupted by phone calls
- If interruptions happen, overhead may be
exceedingly high
phone call app switch
Daily interruptions (% usage) 3.2 (2.2) 8.3 (5.3) per user
Regular app runtime (s) 24.8 (31.8) 18.9 (24.4)
per app
Overhead duration (s) 43.2 (65.9) 34.4 (40.7)
per app
mean (SD)
11
12. Re-Design of Phone UIs
plementation
ved form single-purpose devices to multi-purpose devices
call applications did not evolve accordingly
s can interrupt concurrent application use
of call applications to allow for higher degree of multitasking
one Call Applications
screen modal dialogs providing only options to accept or decline call
ditional third option besides accept/decline to allow user to return to previous application
user to keep attention in previous application while call is pending
tions: Puts incoming call into background for user to pickup call at will
ompletion: Wait until task is done and display call when user leaves previous app
CALLER NAME
CALLER NAME
b) Postponing calls c) Multiplexing d) Background notification
Interruptions do not happen as often as expected
- Extending the design space for phone call UIs
- New interaction design for phone call handling
- Support for better multitasking with call notifications
- Application CallHeads deployed on app store (30,000 users)
12