Open Wearables Release 0.3: Android, Google Health Connect, Samsung Health
Key takeaways
- Google Health Connect and Samsung Health are now supported. Android platform coverage is complete.
- One unified SDK payload format shared across Apple HealthKit, Samsung Health, and Google Health Connect.
- One-click Railway deployment. No local Docker environment required for evaluation or demos.
- Garmin reliability overhaul: backfill rebuilt, user permissions corrected, deregistration webhooks added.
Open Wearables 0.3 is available on GitHub. This is the first stable release in the 0.3 line, consolidating the alpha (Flutter SDK, MCP Server) and beta (Strava, Apple Health SDK maturation, data source priority).
Android platform support
Google Health Connect and Samsung Health are the two primary health aggregators on Android. Both are now supported. The SDK payload format was redesigned to be shared across Apple HealthKit, Samsung Health, and Google Health Connect, which made adding both Android aggregators possible in a single release.
Open Wearables now covers all three major health aggregators: Apple Health on iOS, Google Health Connect and Samsung Health on Android. One API, one data model, regardless of platform.
Railway deployment
One-click deployment on Railway. Useful for evaluation, demos, and teams that prefer managed infrastructure over running Docker locally. The existing Docker Compose path is still the recommended option for production self-hosting.
Garmin overhaul
The Garmin integration received a comprehensive reliability pass: historical backfill rebuilt from scratch, user permissions corrected, deregistration webhooks added to handle account disconnects cleanly.
What's next
0.4 adds Oura Ring, React Native SDK, raw payload storage, and production infrastructure improvements.
Want to see it in action? Book a demo
