Home
I've been jamming on the main feature set and UI elements, and it's now stable, so I've frozen the code for the v.1.0 release. That said, this is still a debug build, but you can clone the repo and build the app in Android Studio on your own and deploy it to your own devices. (Because it's not a built app yet, make sure to deploy the "mobile" module to your smartphone and the "wear" module to your smartwatch.)
This particular approach also uses the Temboo Library for Fitbit, with the OAuth 1.0 credentials used by Fitbit and HTTP requests to the Fitbit API handled by Temboo. You could rebuild this using the more traditional approach and embed the authorization URL in a WebView on the handheld device to grant access to WaterLogg for Wear and handle the networking yourself, but I opted for the path of least resistance.
There was an initial bug with the receiver service on the handheld not unlike that reported by Philipp Adam on StackOverflow. The glitch prevented the message sent from the wearable to the handheld from being handled, such that the onMessageReceived() method only fired every 2nd, 3rd, 4th...Nth time, but not on the initial call.
It's been fixed by increasing the connection timeout, as apparently the time to create the service on the handheld - which isn't sticky (this is key) - outlasted the time to establish a connection on the wearable.
I've got a lot more ideas about how to extend this service, while still keeping the goal of microinteractions in mind. I'd love to hear your feedback!
You can find out more wearable tips in my book, Designing and Developing for Google Glass, by O'Reilly & Associates. Thanks for your support! :)