PeakU · Research

One coach, all your data: why five fitness apps stall progress

Your watch, your lifting log and your run tracker each see a third of you. The acute-to-chronic load research shows why the missing two thirds is where injuries hide.

By the upeak team3 min read1 source
2.1M3.4T2.8W4.9T3.1F3.6S1.4SWeekly load in arbitrary units: runs, lifts and everythingelse, on one scale

Key takeaways

  • Injury risk tracks the ratio of this week's load to your recent average, and only a complete load count can compute it.
  • The recovery question is cross-domain: lifts affect runs, sleep affects both.
  • Unification should mean reading the apps you already use, not adding another one to log into.

The serious self-tracker does not have a data problem. They have a fragmentation problem: the watch knows the sleep, the lifting app knows the squats, the run app knows the tempo, and nothing knows all three. The person is the integration layer, and the person is tired.

Load is only meaningful in total

Tim Gabbett's work on the acute-to-chronic workload ratio made a simple point that the industry has spent a decade proving: injury risk rises when this week's load spikes relative to the last four, regardless of the absolute number. A ratio above about 1.5 was associated with a sharp rise in injury in the original cohorts.

The ratio only works if the load is complete. A heavy leg day counted by the lifting app and a tempo run counted by the run app are, to each app, moderate weeks. Added together they are a spike. No single-purpose app can see it, so no single-purpose app can warn you.

Recovery signals are cross-domain too

Yesterday's squats depress today's HRV. Tonight's short sleep will make tomorrow's threshold run harder than the plan assumes. The lifting app never sees the HRV; the run app never sees the squats; the sleep app sees neither. The question a coach is actually asked, can I train hard today?, needs all of them in one place.

Why the fix is not another app to log into

Adding a sixth app that asks you to re-enter what the other five already know is how most "unified" products fail. The data already flows: Samsung Health, Garmin, Whoop, Oura and Polar all write to Health Connect on Android; Hevy and Strava have APIs. The missing piece is a reader that sits on top, not another logger.

What PeakU does with the whole picture

PeakU reads sleep, HRV, resting heart rate, steps, weight and workouts from Health Connect, strength sessions from Hevy and runs from Strava, and reconciles them into one timeline with duplicates removed. Load is computed across everything on one scale, the ACWR is shown with its drivers, and the coach answers in terms of your actual week: your HRV is 12 ms under baseline and you squatted heavy yesterday, so keep the session but drop the squats. You keep logging where you already log. PeakU is the one place you go to understand it.

PeakU is built for this

A coach that reads everything you already track. Coming soon, free during the beta.

Explore PeakU

Questions

Does PeakU replace Hevy or Strava?
No. It reads them. Lifting routines it builds are pushed back into Hevy so you train in the app you already use.
What if I only have one source connected?
It works with one and improves with each. With only a watch, you get readiness and recovery; add Hevy and Strava and the load picture becomes complete.
Is the acute-to-chronic ratio settled science?
It is contested in detail and useful in practice. PeakU shows it as one driver among several and never lets it raise intensity on its own.

Sources

  1. Gabbett T.J. (2016). The training-injury prevention paradox: should athletes be training smarter and harder? Br J Sports Med. https://bjsm.bmj.com/content/50/5/273