Improve editor and driver effectiveness by reconfiguring "Map issue" and "closure" app buttons
Many drivers report temporary closures as map issues instead. This is very frustrating for us map editors! Temporary closures are extremely hard to diagnose, and often a waste of time to try, because many closures are already over by the time we see the reports. The fact that Waze under Apple CarPlay does not even provide access to the “Closure” feature has made the situation worse.
Please reconfigure the app's reporting tree to make closures more intuitive. I suggest renaming "Map issue" to "Route issue" (in English, something similar in other languages). This is how drivers already seem to perceive this button anyway. Then, put "Closure" underneath "Route issue", rather than as its own top-level button. (This may also be an easy way to make closures available under Apple CarPlay?)
I’m aware that this is, strictly speaking, an app suggestion. Some might argue it doesn’t belong in the WME suggestion box. I suggest it here because this relatively minor change to the app could dramatically improve the volunteer editor experience! Not to mention the improvement in drivers' closure-reporting effectiveness.
Simply reordering the buttons will help. Closure needs to be MUCH higher on the list.
Row 1) Traffic, Police, Crash and Hazard are all things Wazers report that are immediately fed to other Wazers.
Row 2) Gas prices, Map Chat, Map Issue and Place --- reorder to Closure, then Map Issue, then Place. Does anyone actually use Map Chat? Why is it higher priority than closure, which is at the very bottom?
Row 3) Whatever is left.