Creating helpful fitness experiences with Health Services and Health Connect
summary
Health Connect stores and shares user health data on-device (Android SDK 28+) with per-data-type read/write permissions and replaces Google Fit by end of 2024. Health Services (Wear OS 3+) provides on-watch sensors and algorithms via three APIs—ExerciseClient, MeasureClient, PassiveMonitoringClient—supports over 80 exercises and now reports exercise end reasons. Typical flow: Pixel Watch caches metrics, uses WorkManager to upload at workout end, phone writes to Health Connect; prefer direct internet sync over Data Layer when iOS pairing or offline conditions apply.
AI-written summary · about
chapters (5)
- 0:00Introduction to health APIs
- 1:34Using Health Connect
- 4:24Using Health Services
- 7:41A combined user journey
- 10:23Implementation best practices
related talks
14mCreating helpful fitness experiences with Health Services and Health Connect
18mIntroducing new APIs for health and fitness in Health Connect by Android
23mHow to Build a Healthcare App in 2022
39mHealth Ecosystem — Opportunities Explored Together
37mHow I Regained Athlete-Level Code with the Google Fit API
02mAndroid Developer Story: Strava sees 30% more daily active users by expanding to Wear OS
28mCreate beautiful, power-efficient apps for Wear OS
26mWellness & Droid