Is your Bowflex collecting dust in the corner of your den? Ready to replace it with your phone? Google Fit is an effort to allow fitness apps to share data in a unified, cohesive fashion. Announced at Google I/O this year, the preview SDK for is now available for developers to explore and start building apps. We're one step closer to the debut of integrated health and fitness services in Android L.
The SDK includes three sets of APIs for developers, as detailed in the Google Developers blog:
- 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 5 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 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 the data like read, insert and delete. When the exerciser finishes her run, the running app can query the History API for all locations during the run and show a map.
With the onslaught of fitness apps taking over the Google Play Store, and companies like Samsung making its own health app a marquee feature on its flagship devices, Google had to conjure up something of its own. The Google Fit service will work with various fitness apps and wearables to store their data locally and in the cloud, and allow fitness apps to share their data with each other.
The SDK is compatible with the new Android L preview for the Nexus 5 and second-generation Nexus 7. You can read more about it at the Developer Preview page.