Your values now flow into mypacing on their own
No more file exports, no more manual uploads: mypacing now has its own app. Install it once, grant Apple Health or Health Connect access, and it syncs your values — heart rate, HRV, sleep, activity and more — completely on its own from then on. Garmin, Oura, Withings & co. are included too, as long as they write into it.

iOS
Available nowThe mypacing app for iPhone is live on the App Store. After you sign in, it asks once for Apple Health access — from then on it syncs new values automatically in the background, including Apple Watch and anything else that writes into Apple Health.
Android
In closed testingThe Android app is fully built and syncs your values via Health Connect — Samsung Health, Garmin, Whoop and anything else writing into it. It is not in the Play Store yet: for apps that help people manage a condition, Google requires an account registered to a company or an association — a small business has been registered for that since 27 August 2026, and the changeover of the Play account is under way. If you would rather not wait, you can install it directly from here — with instructions, a checksum, and what you should know before you do. And even without the app, mypacing works fully as a web app in your browser on Android, with the same analysis.
How the automatic sync works
Install the app & register for free
Download the app (App Store for iPhone, Android still in closed testing — direct download) and create your free account — the same account you already use on this website.
Grant Health access once
On first launch, the app asks for access to Apple Health or Health Connect. You decide exactly which values to share — and you can change that permission at any time in your device settings.
Done — mypacing keeps reading on its own
From here on, mypacing fetches new values automatically in the background, with nothing left for you to do. No export, no upload, no ZIP files — your analysis and your exertion review get sharper with every new day.
Which device paths are actually supported
“Supported” can mean three different things. This table therefore separates automatic app sync, automatically parsed file imports, and manual review only. No direct manufacturer account-to-account connection is live at present.
| Source / device | Path | Automatic? | Important limitation |
|---|---|---|---|
| Apple Watch and other sources in Apple Health | iOS app → Apple Health | Yes, after permission | mypacing can only read data types actually present in Apple Health and granted by you. |
| Samsung, Pixel, Garmin, Whoop, Oura, Polar, Withings & others on Android | Android app → Health Connect | Yes, if the provider app writes the relevant data type into Health Connect | Not every provider writes every value. HRV may also use different metrics or time windows by provider. |
| Apple Health export, Garmin Connect/FIT, ResMed/CPAP, Whoop, Visible | File via data upload | Parsing yes, upload by you | No ongoing manufacturer-account sync; one historic export is enough to start and later refreshes are optional. |
| Fitbit, Oura, Withings, Polar and other unknown export files | No automatic account import for those export formats at present | No | Manual review can be requested; that is not a promise that the format is already importable. |
| Direct manufacturer accounts (Garmin/Oura/Withings/Polar/Whoop/Suunto/COROS etc.) | Planned direct API connections | Not live yet | No date promised. Connector groundwork in the code does not by itself make a product feature available. |
As of 12 Sep 2026. The actual data path matters, not the logo on the watch. For HRV, mypacing also does not silently treat SDNN and RMSSD as the same measurement.