Open Wearables Release 0.3 Beta: Strava, Apple Health SDK, Data Source Priority
Key takeaways
- Strava joins as the seventh supported provider. Activity data flows through the same normalized API.
- Apple Health SDK now uses invitation codes instead of manual SDK tokens. Refresh token support added for persistent sessions.
- Data source priority is configurable at provider and device type level. Controls which value wins when multiple devices report the same metric.
- MCP Server updated with workout data retrieval and activity listing tools.
Open Wearables 0.3 beta is available on GitHub.
Strava
Strava is now a full provider. Activity and workout data normalizes into the same schema as Garmin, Polar, Whoop, and other supported providers. No separate query logic needed for Strava users.
Apple Health SDK maturation
Onboarding now uses invitation codes. Generate a code through the API, give it to the user, the SDK handles authentication from there. Removes the need to build a custom token-passing flow in your mobile app.
Refresh token support means sessions persist across app restarts. Background sync continues without re-authentication. Structured logging with batch tracking added for debugging sync operations in production.
Data source priority
When multiple devices report the same metric (Apple Watch and iPhone both tracking steps, or Garmin and Apple Health both recording an activity), you now control which source wins. Configurable at provider level and device type level.
MCP Server updates
New tools for workout data retrieval and activity listing. Health data presentation prompts added for common LLM query patterns.
What's next
0.3 stable adds Android platform support: Google Health Connect and Samsung Health.
Want to see it in action? Book a demo
