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.
Apps WorkOutDoors: New workout features
- Thread starter cfc
- Start date
- Sort by reaction score
Just to add, excellent results with the beta so far.
Have used it with routes created on Plotaroute, with my own Waypoints. Exporting as a .FIT file retained the symbol types, so I had arrows or whatever as I came up to the Waypoints.
(as reported, I can force a repeatable crash in the phone app, but its easy enough to avoid).
Have used it with routes created on Plotaroute, with my own Waypoints. Exporting as a .FIT file retained the symbol types, so I had arrows or whatever as I came up to the Waypoints.
(as reported, I can force a repeatable crash in the phone app, but its easy enough to avoid).
Another good test today - navigated 35k successfully...the "upcoming Waypoint" and then "at the Waypoint" alerts are so useful - possibly now could get away with defaulting away from the map screen in some circumstances when navigating, and just flip to the map screen for a bit of clarification where required.
One question - am I missing a setting hidden away somewhere? Today I did a parkrun (5k), then stood about for 10-15mins waiting for some friends to finish, I then had 30km to run home...I'd intended doing the whole 35k as a single activity, but I glanced at the screen before setting off on the 30k, and it was on the 'Done' screen...and the parkrun was recorded as a 39:52 long activity (I'd actually finished in about 25mins).
I have the "confirm end workout?" enabled, so highly unlikely to be spurious presses/rain drops I'd have thought. I *did* press lap to drop a marker as I finished the parkrun, but definitely was still "in the activity" after doing this...not paused, not ended.
Is there a timer somewhere that ends an activity after no motion for 15mins?
Could do with finding and disabling this, I've got an 115k Ultra next week ("The Wall") which may involve some lengthy check point delays 😅
One question - am I missing a setting hidden away somewhere? Today I did a parkrun (5k), then stood about for 10-15mins waiting for some friends to finish, I then had 30km to run home...I'd intended doing the whole 35k as a single activity, but I glanced at the screen before setting off on the 30k, and it was on the 'Done' screen...and the parkrun was recorded as a 39:52 long activity (I'd actually finished in about 25mins).
I have the "confirm end workout?" enabled, so highly unlikely to be spurious presses/rain drops I'd have thought. I *did* press lap to drop a marker as I finished the parkrun, but definitely was still "in the activity" after doing this...not paused, not ended.
Is there a timer somewhere that ends an activity after no motion for 15mins?
Could do with finding and disabling this, I've got an 115k Ultra next week ("The Wall") which may involve some lengthy check point delays 😅
Glad the beta is working well. Do you still get that crash in the waypoint screen of the iPhone app with the latest beta (v6.0.2)? I couldn't reproduce the bug (although someone else also reported it) but I have added some 'defensive' code that may help.
Please send me the wkt file for that workout and it should tell me the reason for the workout ending. To do this tap the Export button 3 times quickly and email to info@workoutdoors.net.
Note that the Are You Sure? confirm message when ending a workout is useful but is not a guaranteed way to avoid accidentally ending a workout. Unfortunately if something (usually a sleeve) is touching then screen then it can also tap the Yes button.
The full water lock is the best way to avoid spurious touches, although even that isn't perfect since Apple changed it to just require the crown to be pressed for a second to unlock. It was much safer in the past when disabling the water lock required the crown to be spun rapidly. However Apple changed that for some reason, and didn't even make spinning to disable an option.
Hello!
I believe I have found a bug, it has been here since the first beta I think. But I forgot to tell, sorry
There’s a new option to navigate and follow a route of a past workout.
Then it shows the available workouts to choose from.
After I choose one, this screen shows and I don’t know what to do…
When I try to click “done”, it just jumps to the prior page and then shows another new workout summary page like before, automatically. And it keeps doing that forever, when I hit “done”, until I kill the app.
I believe I have found a bug, it has been here since the first beta I think. But I forgot to tell, sorry
There’s a new option to navigate and follow a route of a past workout.
Then it shows the available workouts to choose from.
After I choose one, this screen shows and I don’t know what to do…
When I try to click “done”, it just jumps to the prior page and then shows another new workout summary page like before, automatically. And it keeps doing that forever, when I hit “done”, until I kill the app.
I must admit that I haven't looked at the target workout functionality for a long time so I may have broken it in the meantime. I will take a look.
Please could you report bugs to my email address rather than posting them publicly: info@workoutdoors.net. People skim-reading this thread may assume they are bugs with the release version rather than the beta. Thanks.
Finally I managed to do some field tests on a longer route and try all the options that are important to me.
Activity: Hiking
Route: 24km in the shape of the letter P with the start and finish at the very bottom and a loop leading through the summit.
AWU1, 2.5yo, battery health: 86%
AOD off, no screen with map, map used about 10 times by double tapping
TL;DR: the app is almost perfect and it was worth the wait
My comments:
- sometimes climbing segments are not recognized properly, but editing is easy and fast and it is not a problem
- adding your own WP/POI is easy and convenient
- transferring maps to the watch - I have the impression that it is much faster than before
1. Since the start and finish were at the same point and the route led for about 3km the same in both directions before it split into a loop, of course at the beginning I got a message that I was going in the wrong direction, but it only took about 10s for the app to figure it out - an impressive result (better than Garmin/Suunto)
2. The distances to the next WP/POI and to the end of the route work perfectly
3. Climb profile is an absolute masterpiece and... I am speechless, it is simply a dream come true for every climber
4. Battery consumption is on average 8.7% per hour, significantly more for the first hour, I assume that it's because of changing WP several times and generally messing around with the application, so I think it's on average about 8%/h. So it should be enough for about 12h (Fitness by Apple ~5-6%/h, enough for ~18h).
5. I asked Ian for the "distance to next+1/next+2 and so on WP" metric to have a list of upcoming WPs, but it turns out that a much better solution to what I wanted to achieve is "dist to chosen WP" because together with the "select WP" button it allows for much greater flexibility depending on your needs.
But there is a problem - the distances for the selected WP did not match at all. Even if I selected the next upcoming WP, the values "distance to next WP" and "distance to chosen WP" were different. Finally I saw that regardless of where I am on the route, the distance to the start and end of the route is exactly the same, which leads me to the conclusion - "distance to chosen WP" shows the distance in a straight line, not according to the route...
If this is true, then I understand such a choice and I can see its applications, but I have a small suggestion - maybe all WP/POI that can be set like this, but those that are selected from the route currently used for navigation could have the distance calculated based on this route? That would be so great
To sum up - excellent work, the best app ever, worth every penny
I am eagerly awaiting the stable version because there is a huge hiking/climbing crowd to whom I want to recommend it (and for obvious reasons I can't do that while it is a beta).
Activity: Hiking
Route: 24km in the shape of the letter P with the start and finish at the very bottom and a loop leading through the summit.
AWU1, 2.5yo, battery health: 86%
AOD off, no screen with map, map used about 10 times by double tapping
TL;DR: the app is almost perfect and it was worth the wait
My comments:
- sometimes climbing segments are not recognized properly, but editing is easy and fast and it is not a problem
- adding your own WP/POI is easy and convenient
- transferring maps to the watch - I have the impression that it is much faster than before
1. Since the start and finish were at the same point and the route led for about 3km the same in both directions before it split into a loop, of course at the beginning I got a message that I was going in the wrong direction, but it only took about 10s for the app to figure it out - an impressive result (better than Garmin/Suunto)
2. The distances to the next WP/POI and to the end of the route work perfectly
3. Climb profile is an absolute masterpiece and... I am speechless, it is simply a dream come true for every climber
4. Battery consumption is on average 8.7% per hour, significantly more for the first hour, I assume that it's because of changing WP several times and generally messing around with the application, so I think it's on average about 8%/h. So it should be enough for about 12h (Fitness by Apple ~5-6%/h, enough for ~18h).
5. I asked Ian for the "distance to next+1/next+2 and so on WP" metric to have a list of upcoming WPs, but it turns out that a much better solution to what I wanted to achieve is "dist to chosen WP" because together with the "select WP" button it allows for much greater flexibility depending on your needs.
But there is a problem - the distances for the selected WP did not match at all. Even if I selected the next upcoming WP, the values "distance to next WP" and "distance to chosen WP" were different. Finally I saw that regardless of where I am on the route, the distance to the start and end of the route is exactly the same, which leads me to the conclusion - "distance to chosen WP" shows the distance in a straight line, not according to the route...
If this is true, then I understand such a choice and I can see its applications, but I have a small suggestion - maybe all WP/POI that can be set like this, but those that are selected from the route currently used for navigation could have the distance calculated based on this route? That would be so great
To sum up - excellent work, the best app ever, worth every penny
I am eagerly awaiting the stable version because there is a huge hiking/climbing crowd to whom I want to recommend it (and for obvious reasons I can't do that while it is a beta).
Finally I managed to do some field tests on a longer route and try all the options that are important to me.
Activity: Hiking
Route: 24km in the shape of the letter P with the start and finish at the very bottom and a loop leading through the summit.
AWU1, 2.5yo, battery health: 86%
AOD off, no screen with map, map used about 10 times by double tapping
TL;DR: the app is almost perfect and it was worth the wait
My comments:
- sometimes climbing segments are not recognized properly, but editing is easy and fast and it is not a problem
- adding your own WP/POI is easy and convenient
- transferring maps to the watch - I have the impression that it is much faster than before
1. Since the start and finish were at the same point and the route led for about 3km the same in both directions before it split into a loop, of course at the beginning I got a message that I was going in the wrong direction, but it only took about 10s for the app to figure it out - an impressive result (better than Garmin/Suunto)
2. The distances to the next WP/POI and to the end of the route work perfectly
3. Climb profile is an absolute masterpiece and... I am speechless, it is simply a dream come true for every climber
4. Battery consumption is on average 8.7% per hour, significantly more for the first hour, I assume that it's because of changing WP several times and generally messing around with the application, so I think it's on average about 8%/h. So it should be enough for about 12h (Fitness by Apple ~5-6%/h, enough for ~18h).
5. I asked Ian for the "distance to next+1/next+2 and so on WP" metric to have a list of upcoming WPs, but it turns out that a much better solution to what I wanted to achieve is "dist to chosen WP" because together with the "select WP" button it allows for much greater flexibility depending on your needs.
But there is a problem - the distances for the selected WP did not match at all. Even if I selected the next upcoming WP, the values "distance to next WP" and "distance to chosen WP" were different. Finally I saw that regardless of where I am on the route, the distance to the start and end of the route is exactly the same, which leads me to the conclusion - "distance to chosen WP" shows the distance in a straight line, not according to the route...
If this is true, then I understand such a choice and I can see its applications, but I have a small suggestion - maybe all WP/POI that can be set like this, but those that are selected from the route currently used for navigation could have the distance calculated based on this route? That would be so great
To sum up - excellent work, the best app ever, worth every penny
I am eagerly awaiting the stable version because there is a huge hiking/climbing crowd to whom I want to recommend it (and for obvious reasons I can't do that while it is a beta).
Agree with all this - I ran 35km...slightly less than 3.5hrs at the weekend and I think drained about 7% per hour, so that would be comparable to your data - I'm guessing that hiking you had more opportunity for fiddling around and checking things than I did!
I loved the hill profile too, I thought I wouldn't really want to see it, I quickly disabled ClimbPro on Garmin as it became confusing what I was looking at, but this view is really nice - especially as you can quickly remove any climbs you're not interested in.
The usual reason for file transfer problems is because you use an audio app on your watch and this is transferring large files. Unfortunately iOS / watchOS only allow one app to transfer data at a time, so when this happens WorkOutDoors has to wait. The reason I mention audio files is because they can be large and take a long time to transfer.
There are a couple of things that may help. Firstly try switching Bluetooth off on both the phone and the watch. If both are connected to WiFi then any data transfers will be much faster and the audio file will finish transferring much quicker. Apple use Bluetooth by default because it uses less power, but it is very slow.
Secondly some people have reported that starting a dummy workout on the watch can help because it gives the app higher priority in the eyes of watchOS. However I can’t confirm this because I never get any file transfer problems (probably because I rarely use audio apps). An outdoor activity type is apparently best because it makes the app use GPS which may increase its priority.
Thanks for the detailed feedback. It's great to hear that it went so well!Finally I managed to do some field tests on a longer route and try all the options that are important to me.
Activity: Hiking
Route: 24km in the shape of the letter P with the start and finish at the very bottom and a loop leading through the summit.
AWU1, 2.5yo, battery health: 86%
AOD off, no screen with map, map used about 10 times by double tapping
TL;DR: the app is almost perfect and it was worth the wait
My comments:
- sometimes climbing segments are not recognized properly, but editing is easy and fast and it is not a problem
- adding your own WP/POI is easy and convenient
- transferring maps to the watch - I have the impression that it is much faster than before
1. Since the start and finish were at the same point and the route led for about 3km the same in both directions before it split into a loop, of course at the beginning I got a message that I was going in the wrong direction, but it only took about 10s for the app to figure it out - an impressive result (better than Garmin/Suunto)
2. The distances to the next WP/POI and to the end of the route work perfectly
3. Climb profile is an absolute masterpiece and... I am speechless, it is simply a dream come true for every climber
4. Battery consumption is on average 8.7% per hour, significantly more for the first hour, I assume that it's because of changing WP several times and generally messing around with the application, so I think it's on average about 8%/h. So it should be enough for about 12h (Fitness by Apple ~5-6%/h, enough for ~18h).
5. I asked Ian for the "distance to next+1/next+2 and so on WP" metric to have a list of upcoming WPs, but it turns out that a much better solution to what I wanted to achieve is "dist to chosen WP" because together with the "select WP" button it allows for much greater flexibility depending on your needs.
But there is a problem - the distances for the selected WP did not match at all. Even if I selected the next upcoming WP, the values "distance to next WP" and "distance to chosen WP" were different. Finally I saw that regardless of where I am on the route, the distance to the start and end of the route is exactly the same, which leads me to the conclusion - "distance to chosen WP" shows the distance in a straight line, not according to the route...
If this is true, then I understand such a choice and I can see its applications, but I have a small suggestion - maybe all WP/POI that can be set like this, but those that are selected from the route currently used for navigation could have the distance calculated based on this route? That would be so great
To sum up - excellent work, the best app ever, worth every penny
I am eagerly awaiting the stable version because there is a huge hiking/climbing crowd to whom I want to recommend it (and for obvious reasons I can't do that while it is a beta).
I will modify the "distance to chosen waypoint" metric to use the route distance instead of the straight line distance for when the waypoint is on the current route. I should probably have thought of that, so thanks for suggesting it.
Exactly. Nothing to distract @cfc from making WOD ever greater! 🙂
Hello,
Not able to wait until it is released ....
What does this 2.0 in green, and this 1.5 in blue mean?
How are the colors distributed in %? Green, yellow, brown, red, ....
Regards,
Jon
Regards,
Jon
Hi! It’s just my heart rate zones. And it’s not a new feature, it is already available on the current oficial version of WOD.Hello,
Not able to wait until it is released ....
What does this 2.0 in green, and this 1.5 in blue mean?
How are the colors distributed in %? Green, yellow, brown, red, ....
Regards,
Jon
Regards,
Jon
Ah, ok. At it is just below the altitude chart I thought 2.0 were the distance and green the average grade.
But the altitude chart it is from the beta, no?
This is just a beta with the new navigation features. It probably won't be released to the App Store for a while, depending on how the testing goes.
Unfortunately I can't ever guarantee that the app will work on a watchOS or iOS beta, especially the first betas of each.
And even if it seems to work with the first betas (and initial indications so far are promising) then Apple could easily change something in future betas that breaks it.
Sorry about that. My usual plan is to wait until about the 4th or 5th beta, when things have stabilised, and then try to make changes to the app that at least fix any showstopper issues when running it on the betas. This year that may fit in nicely with the release of the new version, but we will see.
Please let me know if you spot any issues with the app running on iOS 26. I have had a quick look and can't see anything obvious but I haven't fully tested it yet.