---
title: "Open Wearables Release 0.4: Oura Ring, React Native SDK"
description: "Open Wearables 0.4: Oura Ring integration, React Native SDK, raw payload storage, provider disconnect API, production Docker Compose."
canonical_url: "https://openwearables.io/blog/open-wearables-release-0-4-oura-ring-react-native-sdk"
---

# Open Wearables Release 0.4: Oura Ring, React Native SDK

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

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

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

## Key takeaways

- Oura Ring is now a supported provider. First integration contributed entirely by a community member (@vikohone via PR #454).
- React Native SDK is live. Cross-platform mobile option alongside the existing iOS, Android, and Flutter SDKs.
- Raw payload storage: archive incoming provider data to S3 for debugging, auditing, and reprocessing.
- Production infrastructure: dedicated docker-compose config, archive and retention policies, provider disconnect API.
- Community milestone: 1,094 GitHub stars, 150 forks, 23 contributors.

Open Wearables 0.4 is available on GitHub.

## Oura Ring

Oura Ring support was contributed by @vikohone through PR #454. This is the first provider integration built entirely by someone outside the Momentum engineering team. Oura data flows through the unified API, normalized into the standard data model. If you're already querying sleep or activity data through Open Wearables, Oura users work without any changes on your side.

## React Native SDK

Completes the mobile SDK coverage: iOS, Android, Flutter, and now React Native. Same authentication pattern and data flow as the other SDKs.

## Raw payload storage

Enable S3 archival of incoming provider payloads before normalization. Useful for debugging data discrepancies, auditing what providers actually sent, and reprocessing historical data without asking users to re-sync.

## Production infrastructure

Dedicated docker-compose config for production deployments separates concerns from the development setup. Archive and retention policies let you control how long raw and normalized data is stored. Provider disconnect API handles the full lifecycle of a user removing their wearable connection.

## What's next

0.4.3 ships Sleep Score and Resilience Score computed natively inside the platform. First release where Open Wearables produces scored health output from the data it holds.

[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)