Yes. This is currently available but only for workouts with fixed length distance or time, or for interval schedules where it is possible to calculate. When I improve the navigation then it will also work when using a route. It uses the average pace up to that point.
I will probably take into account altitude when calculating ETA in the future, but not in the first version with navigation improvements.It's been my dream for years to have a system that would predict ETA not based on pace so far, but using an algorithm that takes into account the altitude profile and average speed on the ascent/flat/descent. The average pace works well on the flat, but it always made me laugh that Suunto tells me that I have 4h to the end of the route, because I've been going to the summit for 4h, while now it will only be descent and it will probably take 2h
But I know that it is not easy to implement and rather poor chance that someone will introduce it. In addition, I learned to estimate times myself based on distance and altitude profile. But one can always dream
PS - I know you don't want to make any plans or promises, but just casual and non-committal - any approximate dates when more or less we can expect new navi functions?
In the past they were equally popular requests but AOD has become much more requested recently. Multiple times a day whereas navigation is requested maybe every day or two.In that case, it's a pity that it's not the navigation that will be implemented first, before AOD
Fingers crossed, keep up the good work
Average speed is based on distance / time, so is dependent upon the accuracy of the "distance" value provided by the sensor. Current pace however is supplied by the sensor in a "pace" value.
It was right on the Activity page, right under the Activity Title. It right between the Distance and Time fields. I think it is a new feature as I hadn't noticed the step count before.
Interesting - I double checked and I definitely don't get step counts displayed on my activities. Maybe this is a new feature and it hasn't rolled out to everyone yet (I have a premium Strava account) and perhaps it is buggy on the Strava side?
I can't see steps either. I will probably wait until more people have reported it before investigating, especially if it is a new feature.
Updating the screen when the app is inactive (wrist down) requires Apple's latest coding language, which is known as "SwiftUI". This appeared long after WorkOutDoors was first released, so the app does not use it, so I need to rewrite the app to use SwiftUI instead of the language I was using, which is called Objective C.
It actually looks almost identical to the current version.
I have no idea. It is too early to tell. I have just tried it on an indoor workout and the battery usage was only slightly higher than normal, which is a good sign.
I must admit that I have never tried using a chest strap for speed and distance so I don't know how accurate they are.
Maybe one day but not in the near future. The app uses Apple's workout system and calibration does not work in that way. I may allow the distance to be over-ridden one day but it is not high priority at the moment.
Would it be possible to turn AOD on or off per activity type in the settings? For example, on hikes and runs I don't personally need AOD because it is easy to raise my wrist when needed and those activities I would prefer less power consumption. But other activities, like biking, it is harder to raise my wrist so I would not mind AOD. Just a thought while you're developing it.
