Independent research desk

Fitness wearable data,
actually analysed

Most comparisons of fitness trackers are written by people who own none of them, quote no sources, and describe testing they never did. StrengthInsight is the opposite: every guide is compiled from vendor documentation, published research, or arithmetic you can check yourself.

We cover what WHOOP, Fitbit, Garmin, Oura and Apple Watch actually measure — and how each metric is derived, including where the derivation is proprietary or estimated rather than measured.

Scope of coverage
Research guides published
25
Platforms compared
6
First-party device testing
0
Uncited claims permitted
0
Free tools
1

Most read

App integrations

Hevy + WHOOP: do they actually connect?

No — and the reason is structural rather than an oversight. What the API asymmetry means and how to run both in parallel anyway.

App integrations

Hevy integrations: what connects to what

A capability matrix for every major pair — who syncs, who exports, and who needs manual work.

Strength data

Tracking strength progression on WHOOP

What Strength Trainer records, what it leaves to you, and the one derived number that makes a trend visible.

Evidence

Does WHOOP recovery predict your lifts?

The effect sizes are smaller than the marketing implies. What the research actually supports, and what it doesn't.

Reading your own training data

Google Health & Fitbit data

Wearables compared

What we don't do

  • Claim to have worn devices for a fixed test period
  • Report correlation figures we can't trace to a source
  • Present an illustrative example as though it were a measurement
  • Give medical advice — wearable scores are not clinical measurements
  • Accept payment for coverage of any product
  • Collect personal data. No accounts, no newsletter, no data sales

Our editorial standards set out the full method and how corrections work. Our disclosure explains exactly how the site makes money — and what that does and doesn't affect.

Frequently asked

What is StrengthInsight?

An independent research publication covering fitness wearables and the data they produce — what each platform measures, how its metrics are derived, how the platforms compare, and how to read your own strength training data.

Do you test the wearables you review?

No. Guides are compiled from vendor documentation, published research, or stated arithmetic, and each says which. Where we use a threshold or convention of our own — such as the plateau definition — we label it as our heuristic rather than presenting it as a published finding.

We also do not run the software, dashboards and open-source projects we write about. That coverage is desk research from official documentation, README files, licence terms and commit history. We have not installed those projects, connected a wearable, or verified a sync end to end, and our editorial standards spell out exactly what that does and does not cover.

Are you affiliated with any of the brands you cover?

No. Not affiliated with, endorsed by, or sponsored by WHOOP, Fitbit, Garmin, Apple, Oura, Hevy, Strava, Amazon, or any other company whose products we cover.

How does the site make money?

Affiliate commissions on a small number of product links. No sponsors, no subscription, no advertising network, no data sales. Guides with affiliate links say so before you reach them, and every link is marked.

Our coverage of software, dashboards and open-source projects carries no affiliate links at all. Where we list a paid service we state its cost and its free alternative rather than earning from it.

Do I need a wearable to use the methods here?

No. Estimated one-rep max, plateau detection and progression trends are arithmetic on a session log. A wearable adds recovery and readiness context, which is useful, but it isn't what turns a log into progress data.

How do I get my strength data out of my tracker?

It depends on the tracker, and it's usually the harder half of the problem. Hevy publishes a developer API and CSV export, which makes it unusually open. WHOOP's public API covers recovery, HRV, sleep and strain but does not expose per-set Strength Trainer data. We retired our own data-extraction guides in October 2026, because the tool they described no longer exists. We now cover the same problem editorially instead: where Google Health and Fitbit data can go in 2026 and what you can build from it.