Add Routines First, Start Them When Ready

Shipped

• Changed preset routine selection so adding a preset saves it to the routine library first.
• Moved load setup into explicit activation, where it belongs, instead of showing it while someone is only adding a preset.
• Kept Start Routine as the moment where activation rules apply, including the Free plan's one-active-routine limit.
• Added a create gate for custom routines, so a Free user who already used the custom routine slot sees the limit before entering the builder.
• Kept editing open for an existing custom routine, even when the Free custom routine slot is already full.

Why

Adding a routine and starting a routine are different decisions.

That distinction matters more than it sounds. A user might want to save StrongLifts, compare it with another preset workout routine, or keep it in the library until the current training block ends. Starting is a commitment: it affects active routine limits, start dates, load setup, and the workout flow.

The old behavior blurred those two moments. It tried to help by moving straight into activation, but that meant a simple library action could trip an active-routine limit or send someone through load setup before they had actually decided to train the routine. That is the kind of friction that feels small in a test run and much larger when someone is only trying to organize the next block.

This release makes the lifecycle cleaner: add first, then start when ready.

Notes

• Presets do not consume the Free custom routine slot.
• Free users can still edit their existing custom routine and add preset routines to the library while another routine is active.
• Activation analytics stay tied to explicit start actions, not passive library saves.

Next

• Keep making capacity limits visible at the point of decision.
• Continue separating library management from workout activation so the app feels predictable before training starts.