Is Strong a good app for hybrid athletes?

It is a good lifting log and it makes no attempt to be more. Nothing in it responds to endurance training, nutrition or recovery, so a hybrid athlete using it is running it alongside at least two other tools and doing the reconciliation between them by hand.

Does Strong track cardio?

Only as a recorded activity. There is no threshold, no zone prescription and no grading, and nothing about your lifting recommendations changes because of it.

Strong vs Hevy — which is better?

They occupy the same category and the choice is mostly interface preference. Hevy has a more active social layer and a slightly more modern feel; Strong has a longer history and a reputation for simplicity. Neither models endurance load, so for a hybrid athlete the choice between them does not change the gap.

Can I add running to Strong?

You can record it. What you cannot get is any consequence — no prescribed band, no grade, no effect on volume recommendations, and no effect on any calorie figure, because there is no calorie figure.

What is the best minimal lifting app?

Strong is the usual answer and it deserves it. Minimal is a genuine virtue in a tool you use mid-set, and adding features to a set logger has ruined more than one app.

Base vs Strong for Hybrid Athletes

What Strong does well

It stays out of the way. The set logging flow is fast and uncluttered. Nothing prompts you, nothing gamifies you, nothing asks you to engage with a feed while you are resting.

It has been around. A long history means a mature, stable product and a large exercise library.

Plate calculator, rest timer, history. The three things you actually touch during a session, all present and all fast.

If lifting is your training and the rest is incidental, this is a reasonable place to stop reading.

What a hybrid athlete has to build around it

Nothing in Strong responds to endurance training, food or recovery. That is scope, not failure — but the consequence is that a hybrid athlete running Strong is running at least three tools:

Strong, for the lifting
An endurance platform, for the running or riding
A nutrition tracker, for the food

And then doing, by hand, the three calculations that need more than one of them:

Is my surplus real? Needs intake, weight trend and endurance volume together.
Should I deload? Needs lifting fatigue, endurance load and recovery markers together.
Were my easy sessions easy? Needs a threshold and the last four sessions graded against a band.

None of those is hard arithmetic. All of them require a person to sit down on a Sunday and copy numbers between apps — which works for about six weeks, until the answers stop being surprising and the copying stops happening.

The comparison

	Strong	Base
Set logging	Fast and minimal	Fast; last session pre-filled as ghost values
Plate calculator, rest timer	Yes	Yes
Exercise library	Large	Large
RIR in the progression rule	RPE stored	RIR, consumed by the progression rule
Endurance prescription	No	From your own threshold
Endurance grading	No	Per rep or time-in-zone
Nutrition	No	Macros, micros, day templates
Measured maintenance	No	From trend weight and intake
Recovery scoring	No	Against your own baselines
Deload trigger	No	Two-signal, reads both loads
Design philosophy	Minimal by conviction	Minimal in the daily loop, deep behind it

Where the two philosophies genuinely differ

Strong's position is that a lifting log should do one thing. That is defensible and it is why it has lasted.

Base's position is that the daily loop should be minimal and the analysis behind it should not be. Logging a set is one tap on values already in the field. Logging a day of food is one tap on a template. Underneath that, a great deal is being computed — but none of it costs you time during a session.

The difference is not "simple versus complex". It is where the complexity is allowed to live.

On RIR, again

Strong supports RPE as a field. What matters is whether anything reads it.

Rep-only progression cannot distinguish twelve reps at 0 RIR — a real ceiling, earn the load increase — from twelve at 4 RIR, where the load was too light and should jump now. Those are opposite instructions and they look identical in a log that stores only reps, or one that stores RPE and never consults it.

For a hybrid athlete this matters more than for a pure lifter, because effort at a fixed load is also your fatigue signal. RIR drifting upward at a constant weight is the clearest evidence that accumulated load — from either discipline — has started masking your fitness. It is one of the four signals that trigger a deload, and it is only available if the number was recorded and read.

When Strong is the better call

You want a set logger and nothing else, deliberately.
Your endurance work is incidental — a couple of easy sessions a week, not a goal.
You already have a system that works and adding a tool would only add entry.
You have used it for years and your history lives there. That is a real cost to moving and it is fine to weigh it heavily.

When the gap shows up

The usual signal is a question you cannot answer from inside any of your apps. "I have been eating in a surplus for six weeks and the scale has not moved." "My squat is stalling and I do not know if it is the running." "My easy runs feel fine but my lifting is worse."

All three are cross-discipline questions, and none of them can be answered from a lifting log.

What to do next

Try answering the three questions above from your current tools. If you can, nothing here is worth switching for. If you find yourself opening a spreadsheet, that spreadsheet is the thing Base replaces.