---
title: "Open Wearables Release 0.3: Android, Google Health Connect"
description: "Open Wearables 0.3: Google Health Connect, Samsung Health, Railway one-click deploy, and Garmin reliability overhaul."
canonical_url: "https://openwearables.io/blog/open-wearables-release-0-3-android-google-health-connect-samsung-health"
---

# Open Wearables Release 0.3: Android, Google Health Connect, Samsung Health

[All posts](https://openwearables.io/blog)

[Releases](https://openwearables.io/blog/category/releases)

Open Wearables Team · Mar 9, 2026 · 1 min read

## 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.

[GitHub](https://github.com/the-momentum/open-wearables) | [Docs](https://docs.openwearables.io) | [Discord](https://discord.gg/openwearables)

Want to see it in action? [Book a demo](https://openwearables.io/book)

## Keep reading

Releases · Nov 3, 2026 · 11 min read

### Open Wearables 0.11.0: daily aggregates and faster summaries

Open Wearables 0.11.0 moves day and session values into their own aggregate tables, adds day, week and month time series, computes missing workout statistics and cuts the heaviest summary from seconds to 25 ms. Contains breaking changes.

Releases · Oct 26, 2026 · 11 min read

### Open Wearables 0.10.0: new dashboard, nutrition data and sync-aware webhooks

Open Wearables 0.10.0 rebuilds the dashboard in SvelteKit, adds 42 nutrition series types with a meal event, tags every data webhook with the sync it came from and splits calories into total, active and basal energy. Contains breaking changes.

Releases · Sep 23, 2026 · 13 min read

### Open Wearables 0.9.0: Google split into two providers, energy renamed, and a long list of API corrections

Open Wearables 0.9.0 splits Google into google_health and health_connect, renames energy to active_energy, disables the Google Health API rollup that wrote duplicated rows, and fixes date bounds, filters and pagination across the API. Contains breaking changes.

## Run it in your own cloud

Open Wearables is open source and self-hosted. Start from the repository, or bring us in to stand it up in your account.

[Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book)