From the DC Rainmaker preview:
"For one, bike computers should notice within 3-5 seconds of a missed turn. Then, they should just automatically re-route to make it work. Just like every other bike computer and phone mapping app does today. I shouldn’t have to wait minutes, then give it specific guidance.
But that’s actually not the biggest limiter. The biggest challenge is that COROS can’t re-route on the device itself. Instead, it has to go via your cell phone to Google Maps to get re-routing information. If you don’t have cellular connectivity, it won’t re-route. Or, if the app connection drops, it won’t re-route.
I’ve discussed this a lot with COROS. Their view is that in 2024, they believe that re-routing can be better done via the cloud, than on-device. And sure, that’s perhaps true if you’ve got always-connected devices. But the fundamental reality of a bike computer is that many people go beyond cellular range. In fact, especially the many gravel riders they sponsored for Unbound, which would frequently be in no-cellular coverage zones
COROS says they aren’t opposed to offline routing longer term, but it’s not a priority right now. Keeping in mind that once a company starts down that offline routing/re-routing journey, history with other bike computer companies trying this (Wahoo, Hammerhead, Sigma) tells us it’s a 2-3 year process before that’s reliable. And those are companies with extensive experience as bike computer companies. Point being, this won’t likely happen (reliably) overnight."