Sync all your fitness data into one dashboard

Your fitness data is scattered across apps

A smartwatch reports steps to one app, a ring reports sleep and heart rate to another, a training platform holds your workout history, and none of them talk to each other by default. Checking five apps to answer "how did I sleep, and how hard did I train this week" isn't a data problem, it's a dashboard problem. On top of that, the same step count or heart-rate reading often gets reported twice, once by your phone and once by your watch, which inflates totals if nothing deduplicates them.

What is fitness data sync?

Fitness data sync covers three different things people usually mean by it: moving data from one specific app to another (a bridge), giving every app a shared place to read and write health data on the same device (a platform health hub, like Health Connect on Android or Apple Health on iOS), or reading from multiple sources and showing them together in one independent view (a dashboard). They solve different problems and none of them fully replaces the others.

Health hub, bridge app, or independent dashboard?

How FitMesh works

The typical flow is: your wearable or its companion app writes data to a platform health store (Health Connect on Android) or FitMesh reads it directly (Apple Health and the Colmi ring on iOS, or an OAuth-connected provider like Strava). FitMesh reads from every source you've connected, resolves overlaps between them, and shows the result in one dashboard. If you opt in, FitMesh can write its deduplicated result back to Health Connect or Apple Health, or export individual workouts to a training platform, only for the specific destinations listed as supporting that in the table below.

1. 1Wearable or companion app (Samsung Health, Garmin Connect, Strava, ...)
2. 2Health Connect (Android) or Apple Health / direct Bluetooth (iOS)
3. 3FitMesh reads, deduplicates, and fuses the data
4. 4Dashboard, and optionally: write-back or export, only where supported

How FitMesh prevents sync loops

Writing fused data back into a health store creates an obvious risk: if FitMesh then reads that same data back on its next sync, it could double-count it or loop indefinitely. FitMesh avoids this with a few concrete rules:

• Write-back is off by default. You turn it on explicitly in Settings for Health Connect and Apple Health separately.
• Every record FitMesh writes is tagged with its own source identifier, and FitMesh's own read pass filters out records carrying that tag, so it never re-ingests its own writes as if they were a new external source.
• When multiple real sources report the same metric for the same period, FitMesh applies per-metric fusion rules (pick the more complete source, fill gaps from others) instead of summing every source together.
• Cross-app export (sending an individual workout to a training platform) is a one-way, user-triggered action, not a background loop: nothing FitMesh exports gets read back in.

Android, iPhone, and the web dashboard

On Android, FitMesh reads from Health Connect, which is fed by whatever companion apps you already have installed. On iPhone, FitMesh reads from Apple Health and can also connect directly to the Colmi ring over Bluetooth, without needing Apple Health as an intermediary for that specific device. The dashboard itself is available on the web in addition to the mobile apps, so you can check your data without opening your phone.

Write-back also behaves differently per platform. On Android, turning on Health Connect write-back exports once at that moment; it doesn't keep exporting automatically as new data comes in, you need to toggle it off and on again to re-export. On iOS, once you turn on Apple Health write-back, FitMesh re-exports after every successful sync.

Privacy, storage, and export

Your data is stored on EU servers. You control every write-back toggle individually, and you can export your own workouts as GPX or TCX files at any time (a Pro feature) via the native share sheet, to keep your own copy outside FitMesh. Saving exports directly to Google Drive is in development.

What FitMesh doesn't do

• It doesn't sync every fitness app to every other fitness app. Check the compatibility table for the specific source or destination you need.
• Sending workouts to Strava, TrainingPeaks or RideWithGPS is still in development, not available today. Saving exports directly to Google Drive is also in development; use the share sheet instead.
• Write-back to Health Connect and Apple Health doesn't cover every metric (no HRV write on either platform, no weight write on Android).
• Write-back timing differs by platform: Health Connect (Android) exports once per toggle activation, not continuously; Apple Health (iOS) re-exports after every successful sync.
• FIT file export isn't available (licensing); GPX and TCX are.

Getting started

1. 1Download FitMesh and sign in.
2. 2Grant Health Connect (Android) or Apple Health (iOS) permission when prompted.
3. 3Connect any additional providers you use (Strava, Garmin, and others) from Settings.
4. 4Optionally turn on write-back to Health Connect or Apple Health once you're happy with what the dashboard shows.