Base vs RP Hypertrophy App for Hybrid Athletes

What RP gets right, and it is the important thing

Most lifting apps track what you did. RP models how much you should be doing, which is the variable that actually governs hypertrophy.

The MEV-to-MRV ramp. It starts a mesocycle near your minimum effective volume for each muscle group and adds sets week by week toward your maximum recoverable volume, then deloads and restarts higher. That is the correct structure and almost nothing else implements it.

Per-muscle autoregulation from your own feedback. After each session you report soreness, pump and performance per muscle group, and next week's set count moves accordingly. The input comes from you rather than from a heart-rate proxy, which is the right choice. Why subjective proximity and recovery signals beat inferred ones.

It has a defensible position on volume. The set counts are grounded in the dose-response literature rather than invented. What that literature actually shows.

Deloads are structural, not reactive afterthoughts.

For a lifter whose only training is lifting, this is close to the state of the art and this page is not arguing otherwise.

The assumption that breaks

MRV is not a personal constant. It is a function of your total recovery budget, and that budget is shared.

Maximum recoverable volume moves with sleep, with energy availability, with life stress — and with other training. A 50-mile running week and a rest week do not leave the same capacity for quad volume. The research on concurrent training is clear that interference is dose-dependent: it is not that cardio kills gains, it is that total load has a ceiling and exceeding it costs you on both sides. What the interference literature found.

RP estimates your MRV from lifting feedback only. So during an endurance block it is estimating a ceiling using an instrument that cannot see most of the load pressing against it.

In practice this fails in a specific direction: it overshoots. The app ramps volume, you accumulate fatigue faster than the feedback questions capture, and the first clear signal is a stalled block rather than a warning.

The second problem: energy

Volume ramping only works if you can recover, and recovery requires energy. RP has no nutrition layer.

A week with two long runs and a volume-ramp week of lifting is a substantial energy demand, and being 400 kcal a day short of it turns a well-designed volume progression into accumulated fatigue with nothing to show for it. How much a hybrid week actually costs. Why under-fuelling a long session shows up in the weight room two days later.

The comparison

When RP is the better call

• Hypertrophy is the goal and endurance work is two easy sessions a week.
• You are in an off-season with no competing endurance block.
• You want the best volume model available and are willing to manage the interaction with cardio yourself.
• You respond well to structured mesocycles and want the app to run them.

RP is a better pure hypertrophy tool than Base is. That is worth saying plainly.

When the gap becomes the problem

The moment endurance volume is high enough to matter. At that point the app's central output — how many sets you should do this week — is computed from an input set that excludes the largest competing demand on your recovery.

The workaround people actually use is to treat RP's prescription as an off-season ceiling and manually hold below it during running blocks. That works, and it means overriding the app's main feature by feel, which is the thing the app existed to remove.

What closes it properly is a volume target that reads your endurance load as an input, and a deload trigger that fires on both signals rather than one. What that looks like when both halves are on one ledger.

Two things worth checking against RP's numbers: your actual weekly hard sets per muscle group, and your endurance ramp rate. If the second is climbing while the first is also climbing, you are ramping two things into one recovery budget, and something will give.