Information on the wazeo page for wayfinders could stand to be updated with newer photo examples of proper application. Correlation with lane guidance and shields might also prove useful as it seems those were not available to use at the time the page was last updated.
I don’t have any suggestions for updating verbiage at this time. I had the page bookmarked in an attempt to adjust one I encounter often to current guidance. Perhaps this one may serve as an example for review.
Ever since Lanes’ release I’ve been meaning to rationalize the content of this page, including by merging in some of the content from the “when to use Continue voice prompt override” section of that article to make “Wayfinder” a one-stop shop for the question “When should I make sure that the Wazer gets an instruction to keep going ‘straight’ or to stay on the road they’re already on?”
It’s mostly still in my head right now, but thanks for the reminder
ya, i was talking with someone the other day about the continue in the wiki and there are several references to it, it would be nice if that was all in one place
FWIW, the examples in the middle of the page appear to be more recent than the rest and are excellent. I was able to apply the rules listed there to configure the fork displayed in my permalink. Lane guidance and shields had been applied previously.
Absolutely, a consolidation certainly appears to be in order, with fresh examples applying all of our newly adopted tools, namely lane guidance and shields. That’s partly why I submitted my permalink in Dallas as a launching point. I’m fairly certain I did this right based on the wazeo but seeing as we can all come up with similar examples now might be a good time to take one and review.
Yes, lots of work to fix up that page, and then we will get shields in iOS production and want to change the guidance to remove the stub thing altogether. Btw, this stub should not have “to” in its name.
Certainly ever changing guidance and the release of feature to production will cause us to revise but I don’t see any reason why it should give us pause to review/revise the present guidance with an eye on making changes in the future.
