I've used turn-by-turn navigation on my watch precisely once, and I really don't recommend it. Last year I did some GPS art. First a small one to practise it, and then a larger one. The experience with my watch the first time was so bad that I carried by bike computer with me on the second one so I could use that for navigation instead.
But yeah, the article itself seems pretty terrible. It almost doesn't even make sense in the points it brings, because most of them seem to be assuming everyone runs precisely where and when she runs.
I have a Garmin Forerunner 935. The first problem was that because it's just giving turn directions and not showing a map (and tbh, a proper map on that screen size and on a wrist that's moving while running wouldn't be especially practical anyway), I missed turns a lot any time there were multiple possible options within a short space.
Then, when I had eventually just given up on relying on the watch and would stop, pause, get my phone out, and look at it for directions, the fact that it was trying to do GPS basically caused the watch to entirely crash. That's definitely a device-specific bug, but it's one that only showed up due to my workarounds to inherent limitations of the form factor.
I've used turn-by-turn navigation on my watch precisely once, and I really don't recommend it. Last year I did some GPS art. First a small one to practise it, and then a larger one. The experience with my watch the first time was so bad that I carried by bike computer with me on the second one so I could use that for navigation instead.
But yeah, the article itself seems pretty terrible. It almost doesn't even make sense in the points it brings, because most of them seem to be assuming everyone runs precisely where and when she runs.
I frequently use navigation on my coros pace 2 to run different routes because I hate running the same routes all the time, it works just fine.
What watch did you use and what didn't you like about its navigation?
I have a Garmin Forerunner 935. The first problem was that because it's just giving turn directions and not showing a map (and tbh, a proper map on that screen size and on a wrist that's moving while running wouldn't be especially practical anyway), I missed turns a lot any time there were multiple possible options within a short space.
Then, when I had eventually just given up on relying on the watch and would stop, pause, get my phone out, and look at it for directions, the fact that it was trying to do GPS basically caused the watch to entirely crash. That's definitely a device-specific bug, but it's one that only showed up due to my workarounds to inherent limitations of the form factor.
Ah OK, it works differently on my watch. I actually have a simple route-map on the watch when using navigation and it works pretty well.