TY - GEN
T1 - UIWear
T2 - 23rd Annual International Conference on Mobile Computing and Networking, MobiCom 2017
AU - Xu, Jian
AU - Cao, Qingqing
AU - Prakash, Aditya
AU - Balasubramanian, Aruna
AU - Porter, Donald E.
N1 - Publisher Copyright:
© 2017 Association for Computing Machinery.
PY - 2017/10/4
Y1 - 2017/10/4
N2 - Wearable devices such as smartwatches offer exciting new opportunities for users to interact with their applications. However, the current wearable programming model requires the developer to write a custom companion app for each wearable form factor; the companion app extends the smartphone display onto the wearable, relays user interactions from the wearable to the phone, and updates the wearable display as needed. The development effort required to write a companion app is significant and will not scale to an increasing diversity of form factors. This paper argues for a different programming model for wearable devices. The developer writes an application for the smartphone, but only specifies a UI design for the wearable. Our UIWear system abstracts a logical model of the smartphone GUI, re-tailors the GUI for the wearable device based on the specified UI design, and compiles it into a companion app that we call the UICompanion app. We implemented UIWear on Android smartphones, AndroidWear smartwatches, and Sony SmartEyeGlasses. We evaluate 20 developer-written companion apps from the AndroidWear category on Google Play against the UIWear-created UICompanion apps. The lines-of-code required for the developer to specify the UI design in UIWear is an order-of-magnitude smaller compared to the companion app lines-of-code. Further, in most cases, the UICompanion appperformedcomparably or better than the corresponding companion app both in terms of qualitative metrics, including latency and energy, and quantitative metrics, including look-and-feel.
AB - Wearable devices such as smartwatches offer exciting new opportunities for users to interact with their applications. However, the current wearable programming model requires the developer to write a custom companion app for each wearable form factor; the companion app extends the smartphone display onto the wearable, relays user interactions from the wearable to the phone, and updates the wearable display as needed. The development effort required to write a companion app is significant and will not scale to an increasing diversity of form factors. This paper argues for a different programming model for wearable devices. The developer writes an application for the smartphone, but only specifies a UI design for the wearable. Our UIWear system abstracts a logical model of the smartphone GUI, re-tailors the GUI for the wearable device based on the specified UI design, and compiles it into a companion app that we call the UICompanion app. We implemented UIWear on Android smartphones, AndroidWear smartwatches, and Sony SmartEyeGlasses. We evaluate 20 developer-written companion apps from the AndroidWear category on Google Play against the UIWear-created UICompanion apps. The lines-of-code required for the developer to specify the UI design in UIWear is an order-of-magnitude smaller compared to the companion app lines-of-code. Further, in most cases, the UICompanion appperformedcomparably or better than the corresponding companion app both in terms of qualitative metrics, including latency and energy, and quantitative metrics, including look-and-feel.
UR - https://www.scopus.com/pages/publications/85034049526
U2 - 10.1145/3117811.3117819
DO - 10.1145/3117811.3117819
M3 - Conference contribution
AN - SCOPUS:85034049526
T3 - Proceedings of the Annual International Conference on Mobile Computing and Networking, MOBICOM
SP - 369
EP - 382
BT - MobiCom 2017 - Proceedings of the 23rd Annual International Conference on Mobile Computing and Networking
PB - Association for Computing Machinery
Y2 - 16 August 2017 through 20 August 2017
ER -