Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Running with the Apple Training app
- Thread starter NME42
- Start date
- Sort by reaction score
Well, it's been a hectic year of work for me, and running has been pretty much an afterthought. Finally getting back into it now that it's the holidays, and well, I can maybe run every other day. Legs need time to rest, knees are starting to give me problems, and boy has my stamina dropped off a cliff.
Nothing to boast about. A very humble 3+ km here and there. 😬
But I do hope to be able to at least over the weekends next year (unlikely to do so on weekdays due to work). Running has been one of the few physical activities I actually enjoy (something about a good sweat that makes all the stress just melt away).
The Bevel app (competitor to Athlytic) is now free in the base version. For someone who wants to have all these body metrics it is a good thing.
www.bevel.health
Bevel - The Everything Health App
Bevel is the AI health companion that turns your data into personalized insights and recommendations across sleep, fitness, nutrition, and more.
www.bevel.health
Yes, if you take care of some things. Of course start with a fully charged AW. Also, I would put in battery saving mode.
Unfortunately been 6 weeks since I’ve been doing other than short easy runs - injury not completely good yet.
Before that though, saving was not an issue
Thanks and get well soon. These six weeks could be exactly before 26.1 was released.
It's an issue from HealthKit API.
I am also seeing this with my own app.
When you store structured workouts, it saves workout with multiple activities.
When finishing workout, HealthKit does a huge processing to associate all HKSamples to each activity, and it's a very huge amount of data.
It takes longer than before and can crash on slow/low battery watches.
It has always been super slow, but it's even slower now ...
Thank you so much for this analysis.
Do you happen to know if Apple is aware of the issue?
I raised bug reports in Feedback Assistant and also via the web form but I am not sure if these reports are routed to /dev/null.
I don't know ...
I have raised an issue 2 years ago ... without any response.
They don't care about small developers and people are faster to complain against a small app developer than against a small startup like Apple.
I have raised an issue 2 years ago ... without any response.
They don't care about small developers and people are faster to complain against a small app developer than against a small startup like Apple.
In watchOS 12 there was the bug that sometimes (not reproducible) that in custom workouts sometimes the GPS track missed after the first segment (typically warmup). Do you think this is the same problem?
Because workoutdoors doesn't use the recommended segmentation of workout with HKWorkoutActivityType (see https://developer.apple.com/documentation/healthkit/dividing-a-healthkit-workout-into-activities)
Apple recommends to use that for intervals segmentation:
Interval training
Use HKWorkoutActivity instances to represent the active portions of the workout. You can create an interval workout for any HKWorkoutActivityType; however, all workout activities must use the same activity type as the containing workout. You can’t mix activities within a single workout.
Workoutdoors use a custom way of segmenting workouts.
I will do the same in a new version of my app.
Last year, I have migrated to the Apple way of doing, but as it's super slow, I will rollback to my homemade solution ...
Last edited:
Not to hijack the subject but do you also use the track mode in your app? Don’t know if it’s an API as well?
I have weird experiences with it where the kilometer splits don’t match up with the displayed distance - when finishing on the track it then jumps a couple of hundred meters back in total distance so the 10.000 meters become 9,97 km
It’s not the 0,3% that is bad - totally okay. But pausing when it says 10,000 meters and pressing end and it changes to another number is off
We can't know what apple does when it finishes the workout ...
In my app, I display the "Apple distance", I have no way to control what is done internally, and when we export to other platforms, there is another processing/filtering (like in Strava).
So it's almost impossible to have exactly the same metrics everywhere.
In a workout app, we can get the distances in different ways:
- GPS: depends on the number of points you collect, the algorithm used to calculate the distance between each point, how you manage innacurate points, how you smooth the path ...
- Pedometer: you get data from motion sensor, without any clue on how it's accurate and calculated ...
- Apple Health distance: the magic distance calculation done by Apple in HealthKit with a combination of pedometer and GPS recalibration. It's the distance / instant speed shown in Apple stock workout app (and in my app).
In my app, I display the 3 distances at the end, but in Apple health, it's only Apple one as I use stock APIs for storing workouts.
It's a super opaque process ... and it's a miracle if we have so small error margin !
In my app, I display the "Apple distance", I have no way to control what is done internally, and when we export to other platforms, there is another processing/filtering (like in Strava).
So it's almost impossible to have exactly the same metrics everywhere.
In a workout app, we can get the distances in different ways:
- GPS: depends on the number of points you collect, the algorithm used to calculate the distance between each point, how you manage innacurate points, how you smooth the path ...
- Pedometer: you get data from motion sensor, without any clue on how it's accurate and calculated ...
- Apple Health distance: the magic distance calculation done by Apple in HealthKit with a combination of pedometer and GPS recalibration. It's the distance / instant speed shown in Apple stock workout app (and in my app).
In my app, I display the 3 distances at the end, but in Apple health, it's only Apple one as I use stock APIs for storing workouts.
It's a super opaque process ... and it's a miracle if we have so small error margin !
Finally got a screenshot of my run as I paused it on the track and one right after pressing end workout. Going from 5,133 to 5,020 is a bit weird and don’t get why.
And here in winter time it has a tough time getting my heart rate right (might have been 140 in the end. Nowhere close to 164)