Apple Watch WorkoutKit explained - what works, what doesn't in 2026

When Apple shipped WorkoutKit at WWDC 2023, it changed what third-party apps can do with the Apple Watch. For the first time, a developer could build a custom structured workout - intervals, targets, recovery - and push it to a user's watch as if it were a native workout.

That sounds simple but it's a quiet revolution. Before WorkoutKit, Apple Watch was a closed garden. Apps could record activities but couldn't tell the watch to follow a specific structured session. Garmin and Wahoo could do this for years. Apple Watch couldn't.

Now it can. But WorkoutKit has real limits. If you're picking an Apple Watch training app or building one, you need to know what's actually possible.

What WorkoutKit can do

The framework supports four types of workout steps: warmup, work, recovery, and cooldown. Work and recovery steps can be grouped into repeated interval blocks. Each step can have:

• A duration target (time or distance)
• An intensity target: heart rate range, speed range, pace range, power range, or cadence range
• A name (so users see "Tempo" or "Hill Repeats" on the watch)

You can build a workout like "20 min warmup → 4 × (5 min at marathon pace + 90s easy jog) → 10 min cooldown" and push it to the user's watch via Apple's NowPlayable APIs. The user opens the Workout app, sees the custom workout in their list, and starts it. The watch guides them through the structure.

That's the good news. Now the bad news.

Five specific limitations you need to know

1. Indoor running workouts only support heart-rate targets

The killer for treadmill runners. If your training plan says "tempo run at 4:30/km for 5 km," you can't push that as a pace-target workout for indoor running. The watch literally rejects pace targets indoors. You have to degrade to heart-rate zone 4 instead.

Why: Apple Watch can't measure indoor running pace accurately enough to alert on it. Outdoor pace is GPS-derived; indoor would need a footpod or treadmill data, which Apple doesn't natively integrate.

2. RPE-based workouts don't sync at all

Pfitzinger's plans use Rate of Perceived Exertion (RPE) as the primary intensity language. Daniels' Running Formula uses "E," "M," "T," "I," "R" effort zones that aren't quite RPE but aren't strict pace either. None of these sync through WorkoutKit.

If you want to follow Pfitzinger 18/55 on your Apple Watch, you have to translate every RPE-based workout into either pace or HR zones manually. That's the kind of work an app can do for you if it knows your recent activities and personal pace zones. Without that mapping, you're back to looking at the plan and guessing.

3. Workouts without intervals often don't push

WorkoutKit prefers structure. A plan that says "Easy 30 min" with no intervals doesn't have a clean WorkoutKit representation. Some apps fake-structure it as "30 min warmup, 0 min work" but that's a hack and the watch UX gets weird.

For a marathon plan that's 40% easy runs, this matters. Either every easy run is a manually-started outdoor run (no structure), or the app does some clever wrapping.

4. Swim workouts are HR-only

If your triathlon plan has swim sessions like "8 × 100m at CSS pace, 20s rest," WorkoutKit accepts the structure but ignores the pace target. The watch will time the intervals but won't tell you whether you're at CSS pace or not.

For pool swimming, this is partially OK because you usually have a pace clock on the wall anyway. For open water, it's a real gap.

5. The watch doesn't show your current target

This is the UX gap that even good developers can't fix. When you're in the middle of an interval, the Apple Watch doesn't have a dedicated data screen that says "You should be at pace X right now." It alerts when you're outside the target range, but doesn't proactively show what the target IS during the work step. You either have to remember from the plan or check the watch face metrics manually.

This is fixable in Apple's hands - Garmin has shown what good real-time interval guidance looks like - but as of 2026 we're waiting.

What changed in watchOS 26

Apple's iOS 26 and watchOS 26 brought a native Workout Builder in the Apple Workout app. You can now build custom structured workouts directly on the watch or in the iPhone Workout app. This makes WorkoutKit-using apps less unique than they were, but it doesn't replace them - the native builder still requires you to manually enter every workout, every week, by hand.

If you're a runner with a single workout type ("4 × 1 km at threshold") you do every week, the native builder is great. If you're following a 16-week plan with 96 unique workouts, you still want a tool that imports the whole plan and pushes each day automatically.

What this means for choosing an Apple Watch training app

If you want a training plan app for Apple Watch:

• Check that it actually uses WorkoutKit (vs just being a logger). Many apps still don't.
• Ask what happens with RPE and indoor workouts. If the app silently fails on these, you'll discover it the hard way mid-plan.
• Check how it handles unstructured easy runs. The cleanest apps treat them as a manual "Outdoor Run" the watch starts in standard mode.
• Watch (literally) for proper interval flow. During a workout, the watch should clearly show which step you're in and how long until the next.

What we're building

Stopa is built around WorkoutKit's capabilities and limitations:

• We push structured intervals as proper WorkoutKit workouts
• We translate RPE and "easy/tempo/threshold" zone labels into pace/HR targets using your recent run data
• We document indoor pace limitations explicitly (your indoor tempo will sync as HR Zone 4)
• We don't pretend swim pace targets work when they don't

The honest answer to "can Apple Watch follow my training plan?" is: mostly yes, with caveats. Stopa is built to handle the caveats so you don't have to.

Join the waitlist if you want it on launch day.

Stopa imports any training plan and pushes the workouts to Apple Watch via WorkoutKit. Pre-launch at stopa.app. Read also: How to use ChatGPT to plan your marathon and From PDF to Apple Watch: the actual workflow.