Google has released a preview version of its Google Fit software development kid, hoping that more developers will start getting to work on fitness apps for Android Wear.
In case you didn’t know, Google Fit is a back-end set of APIs that Google wants devs to use in order to take advantage of its cloud-based fitness tracking service. The idea is that devs can access a wealth of data on each user, pooled from multiple fitness apps, and stored in the cloud.
This will obviously play a big role in wearables and also, eventually, in the ‘internet of things.’ For instance, Google Fit can open-up access to data from connected scales, running apps, fitness bands and more.
Here are the three sets of APIs included in the SDK, as described by Google.
- Sensors API provides high-level access to sensors from the device and wearables—so with one API your app can talk to sensors, whether on an Android device or a wearable. So if you’re making a running app, you could register it to receive updates from a connected heart rate monitor every five seconds during a user’s run and give immediate feedback to the runner on the display.
- Recording API allows apps to register for battery-efficient, cloud-synced background collection of fitness data. For example, a running app could ask to store a user’s location so it can map the run later. Once it registers for these data types, collection is done by Fit in the background with no further work needed by the app.
- History API allows operations on data like read, insert, and delete. When an exerciser finishes a run, the running app can query the History API for all locations during the run and show a map.
To access the new SDK developers need to download the latest version of Google Play services. You can currently access local fitness history on a device via the SDK, but the cloud aspect of Google Fit has yet to fully launch. Google says the full, non-preview, version of the SDK will release later this year.