Wearable Computing Devices

Background

Commercial wearable computing devices have become part of mainstream culture. Starting with the FitBit for fitness tracking, through the Samsung Gear and Motorola Moto360 which give text, email, weather, and many Android Wear apps, to the Apple Watch with Apple Pay NFC capability on the wrist, there is an almost overwhelming choice of products.

One of the popular claims of all these devices is that they will promote good habits: better fitness, better nutrition, breaking bad habits, being on time and informed. This is done through a combination of reading a number of different behavioral and physiological sensors on the "smartwatches", and software released by the smartwatch distributors and independent app developers: Google Fit, Apple Health, Microsoft Health. One key argument for the advantages of smartwatches over smartphones in this area is that the smartwatch is in constant contact with your skin and sensor information can be read continuously. Also, haptic feedback (vibration) to get your attention is more effective on the wrist than on a phone, which may be on a table or in a purse.

This project is a continuation of last semester's project, see 2016 Fall Project Paper. Last semester's project investigated the effect of data security perception on wearable device acceptance. Although equipment was ordered last semester, including athletic vests and shorts, it did not arrive in time to collect data and perform analytics on the data.

Project Description

The focus of the study this semester will be on collecting data from the wearable devices and performing analytics on the data. The study will use the devices available from team members and from the capstone program, including athletic vests and shorts, and devices such as Samsung Gear w/Android phone and Moto 360 w/Android phone. Team members having their own wearable and phone pair will be given priority for this project.

We are particularly interested in the security of the data obtained from the wearable devices. The security protocols in transferring the data from wearable devices to smart watches or phones should be described in detail.

The team can start with available software apps, including "trigger" for reminders and starting programs based on a variety of criteria. Interviews and surveys might be conducted if a sufficient number of smartwatch-smartphone users can be located, perhaps an Internet survey. Also, people on the team interested in programming can write apps in Python or Java using smartwatch APIs.

Project Deliverables