| ONCE , or on every occurrence with EventType | Enable activity-aware experiences, including the ability to detect an ongoing exercise started from another app |
|---|---|
| Note: Health Services is available on Wear OS API level 30 | This API is not intended for background capture or workout tracking |
All of these allow developers to focus on developing unique features and user experiences, while relying on the platform to provide robust and consistent metrics in a power-efficient manner.
16| How Health Services helps app developers Without Health Services, apps had to connect to one or multiple sensors, configure each of them appropriately, receive raw sensor data, and use their own algorithms to derive meaningful information | Ensure data consistency across all applications on the same device by using standardized platform computations |
|---|---|
| Testing with synthetic data To test that your app is receiving data updates from Health Services, manually set your device to emit data as if a user is engaged in an exercise | For example, to set a milestone every time the user runs 1 kilometer, use 1km as the initial threshold and 1km as the period amount |
With ExerciseClient, your app can manage a user's workout, set exercise goals, and listen for updates about the current exercise state.