The integrations that matter are the ones your clients already use. Cover four families: wearables (Oura, Whoop, Apple Watch, Garmin, Fitbit, Polar, Ultrahuman), connected scales (Withings), training apps (Strava) and nutrition apps (MyFitnessPal, Cronometer), plus lab results stored over time. The platform must sync automatically, deduplicate overlapping sources and let the client keep their own device. If a client has to retype numbers from one app into another, it does not really count as an integration.
Why double entry kills the follow-up
Manual logging works for two weeks. After that, the busiest clients, who are often the premium ones, stop filling in forms, and the coach loses visibility exactly when it matters. Every field a client has to type twice is a reason to drop out. What you want is simple: the client connects once, the data flows on its own, and the practitioner never copies numbers between tools.
The integration families to check
| Family | Examples | What it brings |
|---|---|---|
| Rings and watches | Oura, Whoop, Apple Watch, Garmin, Fitbit, Polar, Ultrahuman | Sleep, resting heart rate, HRV, activity, training sessions |
| Connected scales | Withings | Weight and body composition trends |
| Training apps | Strava | Sessions, distance, duration, effort |
| Nutrition apps | MyFitnessPal, Cronometer | Calories, macros, protein, micronutrients |
| Lab results | Blood panels relevant to the protocol | Biomarker trajectories with reference ranges |
| Client context | Goals, history, stress factors | The meaning behind the numbers |
The technical pitfalls behind "we integrate with everything"
- Duplicates: a client wearing a ring and a watch reports sleep twice. The platform needs a rule for which source wins.
- Units and definitions: HRV, sleep stages and "readiness" are computed differently by each brand. Compare a client to their own baseline, not across brands.
- Sync that depends on the client: some integrations only sync when the client opens an app. You end up with gaps that look like drift.
- Imposed hardware: a tool that only works with its own device adds cost and friction for clients who already own one.
- One-way data with no consent model: the client should see what is shared and be able to revoke it. The CNIL publishes technical recommendations on sharing data through APIs worth reading before you choose.
Five questions to ask before signing
- Which of the devices my clients already own are supported directly?
- Does data sync in the background, or only when the client opens an app?
- How are overlapping sources (ring plus watch) handled?
- Can I keep my training planning tool (TrainingPeaks, Nolio) and still see sleep and recovery next to it?
- Can the client export or revoke their data at any time?
How Biokub handles integrations
Biokub integrates with 60+ devices and apps, including Oura, Whoop, Apple Watch, Garmin, Fitbit, Polar, Withings, Strava, MyFitnessPal, Cronometer and Ultrahuman. Clients connect their devices once through Folo, the companion web app, and data then flows automatically to the practitioner dashboard: no spreadsheets, no manual logging. Clients keep the device they already own. If you already plan training in TrainingPeaks, Nolio or Garmin Connect, keep it: Biokub sits on top as a correlation layer that crosses training load with sleep, HRV, labs and lifestyle. Consent is explicit, and clients can export or revoke their data at any time.
Once the data flows in, the next question is what to do with it. That is the subject of why wearable data alone is not enough.