The current version does not work with the fitness machine Bluetooth protocol because that is more complicated than all the other protocols put together. It has completely different data formats for rowers, treadmills, steppers etc.
Here are the highlights. However there are literally hundreds of other minor changes throughout the app.
Any operating system will/should do that to prevent the whole system crashes/freezes. Question is, if the memory manager does return an errorcode or throw and exception to handle things gracefully in the app before it happens. I have never programmed for WatchOS, so I can't say.
Oh yes, and for using far less memory than the average iPhone app would use. I guess it makes sense because most apps are relatively simple, but WorkOutDoors is not, mainly due to the map.
If watchOS does allow the app to handle it gracefully then I do not know how to trap it.
I'm happy to report I did a 71 mile gravel bike ride a week ago and had no issues with WOD, and watchOS didn't kill it. I was using Thunderforest maps pre-downloaded, a route, and the ride took 6:42 to complete. My biggest issue was battery drain and I using 50% of my watch battery the first 50% of the ride. I put the watch into theatre mode which helped a lot the 2nd half. My guess is riding gravel with AOD wakes the watch up very often.
Sorry, that isn't possible. No-one has ever asked for that and I feel that it may be a configuration setting to far (if that is possible with WOD).
I may add that in the future. Thunderforest probably provide the data, and if so then it would just be a case of me changing the code to draw it.
Because walkers are usually interested in their speed but runners are usually interested in their pace.
I think it takes a while for the update to get through Apple's systems. I asked for it to be slowly released over a week in terms of the people who have automatic updates enabled, but if you manually look at the App Store then the latest version should be available on both the iPhone and watch App Stores. In theory.
Yes, it would be great if you added the peaks’ elevation as well - seems like a must with hiking!
.
Those changes in activity type functionality are very rarely requested (if ever in some cases) but I will add them to my list and have a think about them.Hi. After Stryd support I can use Workoutdoors as my goto activity tracker on Apple Watch again
Because of that, I have some hopefully relatively simple wish/suggestion to make workoutdoors more accessible. Workoutdoors has lots of options, but they are unnecessarily complicated to navigate for a simple reason. Today there is a lot of noise from activities I am not using and if I want to change some settings, it is rarely across multiple activities but settings for specific activity I am about to use.
My Eyesight is not the best anymore and I don’t always wear classes
- Change the order of the menu-hierarki in settings, so you first choose an activity and find all settings for that activity.
- In settings put activities last, that is not shown in menu. Possible below a separator line or under an “Other”/”Not shown” menu-item.
3. An option to keep the order of activities fixed in the main menu, instead of last used.4. Most of the text does not adapt to the font size set in watch and phone settings5. It would nice if the top+bottom line + labels could be disabled in activity screens to allow for maximum font-size for data. Possible so you can toggle it with a shortcut.
I know 4 and 5 might be difficult in the current implementation, but hope you keep it in mind if/when you transition to SwiftUI.
Thanks for Stryd support and a great app.
No - you can only choose to get the pace from the sensor or from the watch. I may allow both in the future, but am starting relatively simple.
Hmmm, now I am confused if you understood what I meant.
I understood, but it would be a relatively big change (although not difficult to code) that no-one else has asked for. I quite like the idea of a Settings option on the "..." menu and may add it when I add "Start Route" to that menu, because otherwise there would be an odd number of options.
Maybe just add them all at the bottom, so you don't have to go down another level.
I don't think it is that hard, actually when setting up an activity I think it is quite naturally to expect where to look. The only exception is sensors. I would expect Sensor pairing to be global, but I quite like and prefer that it is activity specific. If I recall correct my garmin connect to Stryd if in range and inform me for activities, where I don't even use Stryd. Or maybe it is Polar ?. A HR-belt is another matter though (I don't have one), but I guess that is just a matter of pairing it in WatchOS settings.
You could keep a global default settings for each of them, maybe below a "Activity defaults" menu-item (because I still find settings to cluttered), which is overruled by activity settings if defined. You could also add a button to the activity settings, that would reset to global default (basically clear them). Also in both places have a text telling, that you can adjust those settings for specific activity under an activity and you can define global settings in settings. You might also add a button in global settings for each of the categories, that would replace activity specific values with default for all
I agree it might require a bigger restructure of the app, but I think you underestimate how much time user spend to locate a setting for an activity, especially when there is a lot of unesserary visual noise to filer (disabled activities). Users might also not discover many features, since they simply are hard to navigate to when you are looking for them.
Where is that? 4 is in the lower end for me. 10 would fit. But better than nothing, Maybe, Since would like to keep them fixed on the watch.