Report Actions

Couple of comments/suggestions:

There are too many steps to report an issue within the app. Sometimes as many as 5. One solution would be to allow the user to customize “hot buttons” that would essentially be macros to eliminate all of the steps.

Another issue is the delay in reporting. If you are traveling at 70mph and pass a police officer, by the time you move through the step(s) you have gone considerably past where he/she was located. An algorithm could be implemented that would take your current speed and a predetermined delay of 10 seconds and then back up the sighting appropriately. The data for your speed is already being collected. Furthermore, the alert is set to .5 miles within report location. If you are traveling 70 mph you will arrive at the report much too soon. Most police offers can acquire you when you are within sight. Change the alert to 1 mile or better yet, adjust it according to your calculated speed. These are easy algorithms to implement.

When you have to look away from the road to enter a report using 5 steps, you are a danger to the drivers around you.

Please address this.

These are all excellent points. Alas, this forum isn’t monitored by staff. This is the forum where US based editors discuss map editing guidelines. The best place to make these suggestions would be in the Waze Suggestion Box.

Thanks for your thoughts.

Forgot to mention that both iOS and Android (but not Carplay or Android Auto) users in the US can report by voice using Google Assistant. Also, if you press and hold the report button, you do get a shortcut menu for the most common report types.

However, time based alerts have been a request for a long time and any added voices to that suggestion would be most welcome.

Another note - the location of the report is saved as soon as you first hit the freport button. So no matter how long you take going through the other presses/steps, the location itself is where you originally hit the orange button.

However, if you’re using the voice command reporting… It records the position as the location where the command processor passes the report to Waze, not where you invoked the voice command.