RunNerd's coaching depth depends on the data your device shares. This page shows exactly what's available with each setup — and how to get the most out of RunNerd no matter what you run with.
Coaching outcomes by device path. Capability rows describe what coaching feels like on each setup, not raw data fields. Cost row at the bottom is the honest price of each path — green is free, amber is paid.
| Apple Watch |
Garmin (native bridge) |
Garmin via intervals.icu |
Garmin via RunGap |
Garmin Direct (coming soon) |
Other devices via intervals.icu |
|
|---|---|---|---|---|---|---|
| Run summaries | ||||||
| Effort & zone analysis | ¹ | |||||
| Lap-by-lap breakdown | ² | |||||
| Cadence coaching | ² | |||||
| Personal records | ¹ | |||||
| Weekly plan calibration | ¹ | |||||
| Real-time sync after run | ³ | ³ | ³ | |||
| Cost to user | Free | Free | Free⁴ | ~$5 / 3 mo⁵ | — | Free⁴ |
1 Heart rate aggregated to ~15-minute intervals through Garmin's native Apple Health bridge.
2 Cadence and lap markers don't transfer through Garmin's native Apple Health bridge.
3 Sync delay of 5–15 minutes after each run depending on third-party service refresh.
4 intervals.icu is donation-supported. Free to use; donations are optional and benefit them, not RunNerd.
5 RunGap subscription pricing as of writing. RunNerd does not receive any portion. Check current pricing
Most of RunNerd's coaching is built on top of Apple HealthKit — the system that collects workout data from your Apple Watch and other connected devices into a single place on your iPhone. When your watch records a run cleanly, RunNerd reads the full picture: pace, heart rate every second, cadence, lap markers, GPS route, elevation. That detail is what lets the AI coach analyze your effort the way a real coach would.
Some devices route data through Apple Health with all that detail intact (Apple Watch is the cleanest example). Others lose pieces in transit — Garmin's native Apple Health bridge, for instance, drops cadence and aggregates heart rate. The matrix above shows which paths preserve which capabilities. The sections below explain what to do about it.
If you run with a device other than Apple Watch or Garmin, the intervals.icu path described above works for most major brands. intervals.icu supports Polar Flow, Coros, Suunto, Wahoo, Zwift, and more — meaning if your device syncs to any of those services, RunNerd can read your runs through the same intervals.icu integration described in Option 2.
Setup is the same: create a free intervals.icu account, connect your device's native service to it (Polar Flow, Coros, etc.), then in RunNerd open Profile → Connections and tap Connect next to intervals.icu.
We haven't individually tested every device-to-intervals.icu combination, so data quality may vary. If you're a serious user of one of these devices and want to help validate the experience, email us at hello@runnerd.ai.
We have Fitbit API credentials and partial integration code, but we don't yet have an active Fitbit beta tester to validate the end-to-end experience. If you run with a Fitbit and want to help us prove out the integration, email us at hello@runnerd.ai.
Once validated, Fitbit will appear as a dedicated row in the matrix above with its own capability breakdown.
RunNerd is built and maintained by Aaron, a solo founder in Smyrna, GA. We are not affiliated with Garmin, Apple, Fitbit, intervals.icu, RunGap, or any of the third-party services mentioned on this page. The alternatives documented here are independent tools that happen to help bridge the gap between Garmin's paused developer program and what RunNerd can offer Apple Watch users today. We don't earn anything from referring users to them, and we'll continue documenting better paths as they become available.
If you have questions or want to share what's working (or not working) for your setup, hello@runnerd.ai is the fastest way to reach me.
— Aaron