I ordered one yesterday, it should arrive on the 23rd. I'll be glad to help you with the beta tests.
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
Thanks. I eventually got one ordered for the 23rd after I gave up on the App Store app and ordered as a guest on the website.
My current plan is to release a watchOS 9 version of the app with the running metrics soon after watchOS 9 is released on Monday. The WOD beta has been tested for a while and seems pretty stable.
After that I will work on the changes for the Ultra, with the aim of releasing a new beta for that a few days after the 23rd (because I want to test it on the real device first). At the moment those changes seem to involve making the most of the new screen size and adding support for the action button.
I registered on this site to thank you for this app. It is great for recording any training.
After many months of use and especially with the latest version:
Finally, it would be great as improvements:
After many months of use and especially with the latest version:
- bug1) I had the same problem as this user with a hiking workout: https://forums.macrumors.com/threads/workoutdoors-new-workout-features.2134687/post-31287823
- bug 2) Additionally, I would like to point out a very annoying bug, with the latest updates and the option to add additional sensors -- THANK YOU FOR THIS-- (Cadence/Speed/Distance).
I have installed 2 sensors (Cadence - Speed/Distance) on an indoor spinning bike. The cadence sensor works perfect, but the speed/distance sensor goes crazy, it shows speeds faster than light. Although in the current version if the sensor fails, it does not appear in WOD (neither the speed nor the distance tab), it is registered in Apple HEALTH. I have multiple workouts under this situation if you need to see any. In Apple Health it shows up as 256km;166km; data in 1 second which for a 20 min session is about 8,000km or more sometimes, as well as incorrect recording of speed used.(In apple health -> Distance cycled).
Finally, it would be great as improvements:
- Request 1) That global SCREENs could be apply for all workouts, as I usually have to modify all screen workouts now to have the same config.
- Request 2) In the next version, you could extend the use of sensors to the "Walking" and "Hiking" workouts (not only running).
- Request 3) I have several HR sensors that I use indistinctly, right now I have to enter before launching the training to select the one I am wearing. It would be possible to make a list of priorities so that the app looks for the 1; 2; n; and finally watch os.
- Request 4) I join the request that you are already working on -a graph like the new Apple exercise heart zone- (I can't wait to try it already) https://forums.macrumors.com/threads/workoutdoors-new-workout-features.2134687/post-31353607
Last edited:
From my limited dev experience: Xcode has been updated and the AWU is in the simulator. I think integration can happen now.
Absolutely, I plan my routes with the Komoot app and then I have to transfer them to GPX and then import them to the WOD app. It would be nice if this workflow was simpler.
I try to maintain as much backwards compatibility as possible. WOD currently requires watchOS 5 or newer (and that is only because Apple changed their workout system significantly for that version). I don't plan to change that in the very near future, so the next couple of versions (firstly for watchOS 9 running metrics and the for the Ultra) should still be fine on the series 3.
However the rewrite for the Always on Display will require me to use Apple's latest coding language (SwiftUI) and that will definitely require a more recent version than watchOS 5. Exactly how recent it will require will depend on what parts of SwiftUI I need to use.
My guess is that the Series 3 will be fine because I doubt that the rewrite will need watchOS 9, but the Series 1 and 2 may not be supported because it may require watchOS 7 (and most likely watchOS 8). However this is only a guess and I can't guarantee it until I have done more investigation.
I assume that I will be able to code and test using the latest development environment, but I won't release a beta until I have actually tested it on a real watch.
I haven't had a chance to look into it yet because I have been away for a few days (I wasn't expecting Apple's event to be so early!). However I am back now and will investigate when I have caught up with all the support work and social media stuff.
I don't know if they have a mechanism for apps to do that and it is very rarely requested anyway. Sorry.
If Komoot allowed routes to be exported in a GPX file then they could be sent directly to WOD. However when I just tried now they only seemed to allow me to share a link and then I could export a GPX from that. Maybe we should ask them to add the ability to directly export GPX files from their app.
Yes, exported TCX and FIT files will include power, which will displayed in Strava. FIT files will also include the new vertical oscillation and ground contact time metrics (although I don't know if Strava can display those).
For the bugs:
1) When there seem to be "dead spots" in the workout, they often seem to be where the app is not storing data when it is not in the foreground. This is due to a very rare bug in watchOS where it doesn't allow the app to run in the background, which causes chaos! To fix it please reboot the watch.
2) Is the cycle speed sensor made by Wahoo? They occasionally do strange things so I advise not using them until I have worked out a fix. Sorry about that.
Requests:
1) Easier copying of screen layouts between activities is on my list but low down. Sorry.
2) Which sensors in particular do you want to use for walking and hiking?
3) Trying sensors in order is on my list but again not very high.
4) The new heart (and pace and power) zone graphs will be in the next version, which should be released next week if the testing continues to go well.
Sorry for the brief replies but this is the most manic time of the year for developers!
This is what you need for Komoot Sync, nothing more.
Connect your smartwatch, GPS computer or e-bike with komoot connect.
Connect your smartwatch, GPS computer or e-bike with komoot connect.
Integrate it and all users will love it.
It is a killer feature on Garmin, Coros, Suunto and Wahoo Devices.
Komoot offers everything you need to add turn-by-turn navigation to your app or device without any additional costs
Last edited:
Hey, the app is brilliant. I've been using the app for a long time during hiking.
Is there any possibility to implement a metric, that shows me the remaining distance and altimeter of a loaded GPS-Route? A few years ago you pointed out that the GPX-Track will only displayed on the map without access of the data and the feature may be implemented in future releases.
Again, thanks for all the hard work on this app!
Best regards
Is there any possibility to implement a metric, that shows me the remaining distance and altimeter of a loaded GPS-Route? A few years ago you pointed out that the GPX-Track will only displayed on the map without access of the data and the feature may be implemented in future releases.
Again, thanks for all the hard work on this app!
Best regards
Yes, this is still high on my to-do list, as part of the navigation improvements that involve the app following the user's position along the route.
This has been my joint top priority along with the AOD for a while but both have been on the back-burner for several months because of the unexpectedly large amount of changes that Apple announced for watchOS 9, and now the changes required for the Ultra. Both of these became top priority due to their releases this month, but once I have dealt with them then I plan to look into navigation and AOD.
The Always on Display won't be in the app for a while because it will be a lot of work. Sorry about that. Updating the screen when inactive requires Apple's latest coding language (known as SwiftUI). This appeared long after WorkOutDoors was first released, so the app does not use it.
I plan to rewrite large parts of the app to use SwiftUI just so that it will work with the AOD. However it will take many months, probably as a background task.