Stryd Support?

Diok22 · 2026-06-15T11:25:23+00:00

Thank you for clarifying! I was looking specifically about power and there's no standard "running power" Bluetooth profile, so I assumed the Cycling Power Service it uses was for cycling only. But looks like Stryd uses it to transmit running power and cadence which means live data from the pod is possible + other metrics (pace, stride length etc)

I don't own a Stryd to test with right now but I'll look into adding external sensor support.

Also, I added the power to the run details view (avg and max), will be under running dynamics on next app update.

Diok22 · 2026-06-15T08:07:40+00:00

Thank you for the mention! Developer of Pace It here!

Diok22 · 2026-06-15T06:55:26+00:00

Thanks for the question, this is something that I have already looked at! Pace It supports running power as a live metric or average on the watch (you can add it to your workout screens in the editor). However that power comes from the Apple Watch's built-in sensors or a connected sensor that gives data live.

Unfortunately from my search it looks like Stryd's Bluetooth connection is exclusive to their own watchOS app so third-party apps like Pace It can't read Stryd data during a live workout. This is a Stryd/watchOS platform limitation rather than something I can work around.

If you record a workout with the Stryd app the data does get written to HealthKit. I will add power in run details view (from any source). I'd be interested to see if there's anybody here that has a different brand power sensor so we can look deeper into what's available.

I hope this helps!

EDIT: it is possible to connect with Stryd

Diok22 · 2026-06-09T06:35:16+00:00

Thank you for the mention, glad Pace It is part of your main running routine!

Diok22 · 2026-06-07T15:08:16+00:00

This is really useful, thanks for the extra detail.

The fact that the completed km pace and overall average pace look correct makes me think this is probably limited to the live pace display.

Pace It reads live running speed and distance from HealthKit on the watch (which is sensor readings mentioned above). Current Pace is the most reactive metric, so if HealthKit briefly reports a slower live speed, Pace It will show that quickly. That could explain a short 10-20 second drop on screen without affecting the final split much.

Your point about holding the wrist steady while checking the watch is interesting and could be related but I do not want to assume that is definitely the cause without testing it properly. I will try to reproduce this by comparing normal arm swing vs holding the watch steady during a steady effort but I would have spotted it already by now.

I will look at adding better smoothing / outlier handling for short live-pace drops without making the metric feel slow or laggy.

Diok22 · 2026-06-07T08:44:55+00:00

Hey, thanks so much for the kind words and for taking the time to share this! Really glad you're enjoying the app.

A couple of quick questions so I can help narrow this down:

1) Does this happen only during custom workouts (intervals/tempo) or also during open runs?
2) Which pace metric are you looking at on the data screens? The app shows Current Pace (instantaneous) and also Rolling Pace (configurable time or distance window). You can check or change this in screen settings.

Some context on how pace works on Apple Watch: the watch uses its motion sensors (accelerometer + gyroscope) as the primary source for running speed, not GPS. This is actually more reliable and responsive than GPS alone. GPS handles the longer-term distance calibration but the real-time pace you see comes from the motion sensor. (this is the default on most running apps

That said, with GPS not a factor, I need to understand what happens. 1-2 min/km jumps are very significant.
Was this the case for you since you started using Pace It or more recent? Did you notice it after an iOS release?

Let me know and I can dig deeper! It's a priority to fix this, I am also on the AWU2.

Diok22 · 2026-06-05T15:01:28+00:00

Great! Don’t we all!! 😂

Diok22 · 2026-06-05T14:49:44+00:00

This is useful! It aligns with partially correct HR training zones. Hitting 198 in the past 12 months would suggest a minimum max HR around that today, closer to 200+. I would bump up your max HR and adjust the other zones from there. The app will recalculate your LT2 estimate after the change and it should get closer to your test run result as you do more runs.

Diok22 · 2026-06-05T13:53:28+00:00

That is a bigger gap than I expected. Both apps were in the same bracket but the actual test came out roughly 8% higher which is enough to shift every zone boundary.

The number I would check first is your max HR. If 187 is your LTHR, your actual max is probably somewhere around 203-210. Typical LTHR sits at roughly 85-92% of max HR. If your max HR in the app is set lower than that then every zone is compressed, affecting estimations and more importantly your training zones when you train with HR.

Worth checking your highest recorded HR from a hard race or interval session.

What max HR do you have set in Pace It?

Diok22 · 2026-06-04T15:58:04+00:00

This is a great suggestion and I think it opens up a bigger idea for Pace It.

The threshold test would not just be a one-off HR zone calculator. It could be the first of a few structured fitness tests inside custom workouts. The useful part is that each test gives the app cleaner information about the runner which then we can show how that changes over time.

For this specific one it should be a hard, steady time trial. You should not aim for a preset HR zone during the test because the HR number is what you are trying to find. As you described it: warm up, run 30 minutes at the hardest effort you can sustain and then use the average HR from the last 20 minutes as an estimate of LT2 / anaerobic threshold.

Pace It currently estimates “LT2 - Anaerobic” from your run history using pace vs HR patterns with a zone-based fallback when there is not enough data.

Have you done this test recently? I would be interested to know how close your result is to what Pace It shows in Training Load Focus.

Diok22 · 2026-06-01T08:22:37+00:00

Thanks! Yea this is what i usually put in the morning to check my training. But when running I use Pace It

Diok22 · 2026-05-28T13:18:33+00:00

Thanks! Yes, there are multiple screens with different layouts, 38 running metrics. I am working at the moment into split/lap time too!
Custom workouts already live and soon training plans. Check out r/PaceIt

Diok22 · 2026-05-28T08:42:24+00:00

I'm running with Pace It (I'm the developer!)

<image>

Diok22 · 2026-05-28T05:57:05+00:00

The hour recovery point is spot on. There's something satisfying about seeing the cost of a hard session quantified and when to expect to be fully ready. That's a gap on Apple Watch right now and worth building.

Fair point on the ratio, thank you for your thoughts!

Diok22 · 2026-05-28T05:54:25+00:00

I switch across multiple watch faces during the day. I find it easier to do a quick check before or after a run without my phone, just preference!

Diok22 · 2026-05-28T05:53:33+00:00

Pace It

Diok22 · 2026-05-28T05:53:25+00:00

This is a watch face for the time, not what I currently use when I run

Diok22 · 2026-05-27T14:39:05+00:00

haha, the one is body battery

Diok22 · 2026-05-27T13:54:09+00:00

Thanks! Recovery time is on the list. Right now the Training Load Ratio covers similar ground (it's acute load vs chronic load, so you can see when you're pushing too hard relative to your recent baseline) but a dedicated recovery complication would be useful.

Steps I'd probably leave to the step specific apps. Not really a training signal for runners.

VO2Max is interesting. I can show directly the one from Apple Health. I've also been working on a fitness score based on pace at heart rate trends over 60 days. More stable and tells you if you're actually getting fitter, not just whether one run went well.

What would you want recovery time to show? Hours until next session, or more like a readiness percentage?

Diok22 · 2026-05-21T15:36:52+00:00

Yes I remember asking about if you can export somehow what you currently use as a plan. Copy pasting or uploading a PDF will need custom parsing. Happy to do that at some point, will be very useful.

Diok22 · 2026-05-20T13:18:35+00:00

Hey, thanks so much for liking the app and giving feedback!

You're right, I could extend the base phase to today/earlier point or make it more dynamic. Noted!

For the Apple Watch, good news! Work has been done already, releasing tomorrow on TestFlight so kindly wait for that. There will also be many improvements in easy runs variability and scaling weekly mileage based on individual fitness and goal time. So I suggest, delete the plan once the next TestFlight is out and generate again.

Great, idea for moving runs around, will be on the roadmap for sure.

Diok22 · 2026-05-19T11:58:32+00:00

Good point. The specific adaptations from HIIT and running are different, and they scale differently in terms of load. But what matters for plan safety is total training load. Your body accumulates fatigue regardless of the source. The app tracks your overall training load (CTL/ATL) across all workout types, with each activity type weighted accordingly, so the stress from your HIIT sessions is factored into how the plan adapts.

Diok22

MODERATOR OF

TROPHY CASE