How it works
It works on "If-this-then-that" logic. A Pebble watch sends it's accelerometer data to an Android app which maps gestures. These gestures are sent to a server made in Flask. These gestures can be mapped to anything. A flick of your hand can push or pull code from Github. A flick of hand can navigate the folders on your PC. You can play audio files. Navigate your phone, PC anything. A gesture can also be mapped to controlling the appliances in your home or office. To demonstrate a few use cases of this functionality, we made a lawn tennis unity game. The game can be played while using the cardboard for virtual reality viewing. Each move is mapped and you can play the game as you would in an actual tennis court.
We used a pebble watch to get the accelerometer values. These values were sent to an Android app which used machine learning to map them to gestures. These gestures were sent as signals to a server hosted on IBM Bluemix. To show the use case, we created a game in unity which can be played with virtual reality experience using Google Cardboard
Challenges I ran into
Sending accelerometer data to Android in real time was creating issues. Sending a vast amount of data such that there is no lag was a challenge. Also, we applied machine learning for the gestures. That posed another challenge.
What's next for Flick
Use hooks and map gestures for practically anything! Make safety features. Make games. Map gestures to controlling laptop, TV etc.
IBM Bluemix Link : http://pebble-flick.mybluemix.net/
When link is opened it shows not found. We used the server to poll the data and to communicate. It does not have a landing page
http://pebble-flick.mybluemix.net/getC This is where we polled the data from.
http://pebble-flick.mybluemix.net/setGesture?q=25 or any code for setting value.