How I Regained Athlete-Level Code with the Google Fit API
summary
A developer describes using Google Fit via the Google Play services Fitness API to collect steps, sessions, distances and estimated calories for a consumer app called Fit Plus (with widget and kilometer summarizer). The talk covers handling Marshmallow-era explicit consent and authentication, practical accuracy problems (wrist heart-rate dropouts, tattoos/sweat, false cycling when pushing a stroller), performance quirks like 35-second step queries, low commercial uptake (~€9.75 revenue, ~150 daily users), and creating a custom data source to obtain correct step deltas.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:54The Digital Office
- 3:25AQUITAINE REGION
- 5:49Activity Tracking
- 8:12October 28, 2014
- 12:55Where is the documentation that explains all this?
- 14:17Google Play services 7.0
- 16:20Connection
- 18:36Marshmallow
- 19:20Managing Data
- 19:37Building a Request
- 22:26Sending the Request
- 25:5035 seconds
- 30:2120 minutes
related talks
18mIntroducing new APIs for health and fitness in Health Connect by Android
14mCreating helpful fitness experiences with Health Services and Health Connect- 14mCreating helpful fitness experiences with Health Services and Health Connect
06mTesting Wear OS fitness apps without breaking a sweat
02mAndroid Developer Story: Strava sees 30% more daily active users by expanding to Wear OS
26mWellness & Droid- 02msees 30% more daily active users by expanding to Wear OS
18mFitness motion recognition with Android wear