Skip to main content

Documentation Index

Fetch the complete documentation index at: https://openwearables.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This roadmap outlines what’s currently available in Open Wearables and what’s coming next. Our goal is to build a comprehensive platform that simplifies wearable data integration and enables AI-powered health insights.
Have questions? Join our Discord community to get help, ask questions, and connect with other developers building with Open Wearables.

​
Currently Available

These features are available for use:

​
Developer Portal

The developer portal provides a web-based interface for managing your Open Wearables integration. It includes:
  • General Statistics: View number of users and data points at a glance
  • User Management: Add users via the portal or through the API
  • User Details: View connected data sources, integration status, and user metrics with visualizations
  • API Key Management: Generate and manage credentials in the Credentials tab

​
User Management

User management is available both through the developer portal UI and via the REST API. This allows you to:
  • Create and manage user accounts
  • Track user connections to wearable devices
  • Monitor user data synchronization status
  • Access user health metrics and visualizations

​
Provider Integrations

The platform supports the following wearable providers: Cloud-based (OAuth):
  • Garmin - OAuth + automatic webhook sync
  • Polar - OAuth + data sync
  • Suunto - OAuth + data sync
  • Whoop - OAuth + data sync
  • Strava - OAuth + webhook sync
Device/SDK-based:
  • Apple Health - HealthKit integration and XML export support
  • Samsung Health - SDK-based data sync
  • Google Health Connect - SDK-based data sync
Users can connect their cloud-based devices through a simplified OAuth flow:
  1. Generate a connection link for your user
  2. User authenticates with their wearable provider
  3. Data automatically syncs to your platform
  4. Access via unified API

​
Workout Data Sync and API Access

Workout data synchronization is available across all supported providers:
  • Automatic background synchronization of workout data
  • Normalized data format across all supported providers
  • REST API access to workout information
  • Historical data retrieval

​
Core Health Data Endpoints

The API provides comprehensive health data endpoints beyond workouts, with normalized access across supported providers: See the data types and unified data model pages for full details on available fields.

​
MCP Server (AI Assistant)

An MCP (Model Context Protocol) server that enables AI-powered health data interactions. This feature can work for both developers and end-users in the applications you build, allowing you to plug it directly into chat interfaces within your product.
  • MCP Server Integration: Plug the AI assistant into your existing chat interface or build new conversational experiences
  • Natural Language Queries: Enable users to ask questions about health metrics and recent workouts
  • Customizable AI Models: Swap models to match your needs and use case
  • Data Exploration: Debug and explore user data through conversation, useful for both development and end-user support
Imagine a scenario where you’re building an application for personal trainers. Thanks to Open Wearables and MCP integration, you’ll be able to easily implement a chat through which the trainer will be able to query in natural language about the latest data from their athletes’ wearables.

​
Raw Payload Storage

Optional storage of raw incoming payloads from wearable providers for debugging and data auditing purposes. Supports multiple storage backends including log-based and S3.

​
Mobile SDK (Flutter)

A Flutter SDK for simplified mobile app integration:
  • HealthKit Integration: Native iOS HealthKit permissions and data access
  • Seamless User Registration and Data Sync: Streamlined onboarding process that automatically creates users in Open Wearables and syncs their health data
  • Background Sync: Automatic data synchronization in the background

​
Mobile SDK (React Native)

A React Native SDK for simplified mobile app integration:
  • HealthKit & Health Connect Integration: Native iOS and Android health data access
  • Seamless User Registration and Data Sync: Streamlined onboarding that automatically creates users in Open Wearables and syncs their health data
  • Background Sync: Automatic data synchronization in the background

​
In Development

These features are actively being worked on and will be available in upcoming releases:

​
Connection Widget

An embeddable widget that allows users to connect their wearables directly from your application, without being redirected to the Open Wearables UI.

​
Webhooks - Real-Time Data Delivery

Webhook support for receiving real-time data pushes instead of polling API endpoints:
  • Registration: Register webhook endpoints via dashboard or API, choosing which event types to subscribe to
  • Automatic Delivery: When new data arrives, a POST request is sent to your registered URL with the event payload
  • Retry Logic: Automatic retries with exponential backoff on delivery failure
  • Dashboard: View delivery history, logs, and success rates
  • Security: Signature verification for payload authenticity (Svix standard), HTTPS requirement
See GitHub issue #99 for details.

​
Health Scores

Platform-generated health scores that provide unified, provider-independent interpretations of health data. Instead of relying on manufacturer-specific (often black-box) scores, Open Wearables will calculate its own default scores based on raw data.
  • Sleep Score - a unified score based on sleep duration, number of awakenings, and sleep stage composition (light, deep, REM)
  • Stress Score - stress level assessment based on available biometric data
  • Readiness Score - recovery and readiness estimation
Health Scores will be fully customizable - developers will be able to adjust parameters and thresholds to match their application’s needs.
Sleep Score is the first Health Score being developed and will serve as the foundation for the broader Health Scores system. See GitHub issue #382 for details.

​
Upcoming Features

​
Health Insights Automations

This will be one of the platform’s most powerful upcoming features - the ability to define intelligent health insights using natural language:
  • Natural Language Conditions: Describe when notifications should be triggered in plain English and system will generate well-constrained conditions based on that
  • Webhook Notifications: Configure your backend endpoint to receive real-time health insights
  • Test Automation: Run dry runs on historical data to see how automations work in practice
  • Human-in-the-Loop: Mark incorrect AI interpretations during testing to continuously improve the system
  • Automation Logs: Review past automation triggers and provide feedback
This feature will enable developers to build intelligent health monitoring systems without writing complex rule engines.
Assume you’re developing an application for elderly care. Wearables data integration could be useful to help family members who cannot be on-site for various reasons monitor the health status of their care recipients. Normally, such integration would take several weeks or months. With the help of Open Wearables and the health insights automations module, you’ll be able to implement low activity notifications for a given day even within one day.

​
AI Health Assistant Widget

An embeddable AI chat widget for user health queries, built on top of the MCP Server:
  • Embed in Your App: Drop the AI chat interface directly into your web application
  • Customizable Styling: Match the widget to your app’s design system

​
Additional Provider Support

  • Fitbit
  • Oura
  • Coros

​
Contributing to the Roadmap

Have ideas or want to help build these features? We’d love your input!
Note: This roadmap is subject to change based on community feedback and development priorities. Features marked as “In Development” don’t have fixed release dates, but we’re actively working on them.