Waze Suggestion Box
- There’s power in numbers! Search through existing suggestions to see if there's someone else with a similar idea and upvote it.
- You can build upon an idea -- simply comment below your fellow Wazer's submission.
- This forum is intended for user feedback and ideas. If you have an issue which needs support, please visit our help center.
- Any comments, feedback, ideas, reports, suggestions, or other information you provide to Waze (part of Google LLC) about Waze products and services (collectively “Feedback”) is not part of your personal data.
- You agree not to disclose, in your Feedback, to Waze any information, such as third-party information, that you are obligated to maintain as confidential.
- Waze has no obligation to use your Feedback.
- By submitting your Feedback in this page, you acknowledge that you are of the minimum age required to provide data processing consent in the applicable country where you are located and that you provide permission to Waze, and its affiliates, to use your Feedback and any information that personally identifies you to improve Waze’s current and future products and services in accordance with Waze's Privacy Policy (waze.com/legal/privacy).
- Please avoid providing any personal information in your Feedback.
- Providing a name, when submitting Feedback, is optional. If you choose to provide your name, it will be publicly displayed in this forum next to your Feedback. You can delete your name and provide your Feedback as an anonymous user at any time.
- or
No existing idea results
- ~ No ideas found ~
19061 results found
-
Invites the user to reports UR to correct the problem himself
When the editor reports an error on the map as UR , the system could send an e- mail indicating the WME and the forum so that it even correct the problem on the map. The idea is to get new editors.
12 votesAdminElla (Waze Team) (Admin, Waze) responded
-
Ability to say 'dont send me this way again' for dangerous turns or bad neighborhoods.
I live in a big city with a long commute and many options to to my destinations. Sometimes the way Waze sends me around traffic is dangerous (i.e. Turning left onto a 5 lane, busy highway just to immediately turn right, or through high crime areas). An option to indicate unsafe guidance and not to suggest it again would be great.
12 votes -
Indicate both start and end of roadworks / traffic
For users that mark the beginning or roadworks / traffic, leave up an icon that they can press to indicate the end of the traffic. From this, work out how long it took me to get through the zone and pass on the info to other users.
12 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Holiday feature to place report pins on awesome residential holiday light displays.
We took our child out last night trying to find great holiday light displays. We founds some good ones but crowd sourcing great displays would be awesome. Especially if the more people tagged a display the more prominent it would appear in Waze.
12 votes -
Dans le signalement des danger Météo, serai bien de pouvoir rajouter : VERGLAS et Givre
Dans le signalement des danger Météo, serai bien de pouvoir rajouter : VERGLAS et Givre
12 votes -
Expensify integration
We use Expensify to report our expenses including milage reimbursement. It would be great if the recorded drives could be used in Expensify.
12 votes -
Add Bus stops.
We're already able to mark parking spots. I'd like to be able to mark where a bus stop is (maybe with route/bus names), be able to toggle it on/off the map and be able to search for it.
12 votes -
Allow Menu and Report buttons to be hidden or transparent
For screens that can suffer from burn-in, the buttons at the bottom of the Android client are very bright and prominent. While I have been lucky that the burn went away on my stock Galaxy S3, it would seem a nice option to be able to modify settings for those buttons. I would think either a "show on tap", or transparent option would be best. Perhaps also changing them to a darker look when in night mode would help too.
12 votes -
Police traffic stop - recording speed
I would like to see an action that is a button always on the app screen displayed that allows you to capture speed and other information about your location, etc., when you are being pulled over by a police for speeding. Allow the user's to review the data at stop point to know their speeds, lets say 5 minutes prior to pressing the ticket button. Also, email the data to the user's email.
12 votes -
LinkedIn integration for work related friends
We all know adding work related contacts and friends to Facebook isn't best practice. But when and where do people use Waze the most? Right, driving to and from and during work. Now wouldn't it be a nice feature if Waze supported LinkedIn integration so that your Waze friend list is a combination of Work (LinkedIn) and personal (Facebook) contacts? Well, then vote.
12 votes -
Custom Road Hazard tags
Allow for custom Road Hazard labels. The current selection is quite general, but it would be nice to have the ability to pre-create custom hazard tags for those times when adding a description isn't possible.
12 votes -
12 votes
-
Ability to declare a suggested route bad
Sometimes Waze suggests routes that are so bad as to be cringe worthy. It would be nice to to be able to report them for review.
12 votes -
Indicator on alert for direction
When an alert is displayed on the map, it is generally impossible to tell whether the alert applies to the current direction of travel or the opposite.
12 votes -
Option to Ignore Construction Zones
It would be tremendously helpful to have the ability to ignore construction zones/certain stretches of road. And if possible with the option to automatically ignore if speeds are less than a certain threshold.
12 votes -
Interchange guidance method in ver. 2.2 is wrong. Revert to 2.0 method.
In version 2.2 (Android & iPhone) the written guidance in interchanges was changed. It tries to look-ahead and gives guidance based on the ramp exiting the interchange.
This is inconsistent with the way guidance worked in version 2.0 and therefore inconsistent with the ramp's naming in the Waze map. It leads to confusing guidance that does not match the actual road signs.
This is really dangerous as it increases drivers' confusion in the interchange.
Please revert the guidance method to the way it was in version 2.0For details see http://www.waze.co.il/forum/viewtopic.php?f=30&t=9996&st=0&sk=t&sd=a&start=15#p59430 (in Hebrew)
12 votes -
Location and type of landmark in search results
For easier identification of a landmark, it could be great, to know the settlement or road which is near it and the type of the landmark, after the name of the landmark, like this:
Shell, Somecity/Route66 (Gas station)12 votes -
Add user report confirmation/cancelation buttons for all events
Add user report confirmation/cancelation buttons for all events, similar to "police/not here". This would allow to refresh the reports in the map by other drivers, provide more 'live' info + quicker cancellation of outdated events.
12 votes -
use Android API for event buttons and text input
to report traffic/event irrelevancy it is darn hard to hit that tiny round button with a caret (>) at the end of the event item. instead I should be able to use a long press on a much broader list item to pop up the menu. also, the menu that pops up ought to be from the API. it would create bigger buttons (better for touch sensitive devices) and makes for a much more consistent device use experience plus it would make it more accessible while driving. More accessible means less accidents.
also text input. there seems to be no way to correct typos a few chars back without using backspace. In Android API text inputs users can easily use the navigation buttons/trackball to scroll to the place of mistake and make a MUCH quicker edit.
to report traffic/event irrelevancy it is darn hard to hit that tiny round button with a caret (>) at the end of the event item. instead I should be able to use a long press on a much broader list item to pop up the menu. also, the menu that pops up ought to be from the API. it would create bigger buttons (better for touch sensitive devices) and makes for a much more consistent device use experience plus it would make it more accessible while driving. More accessible means less accidents.
also text input. there seems to be no…
12 votes -
User Report: option to share destination
Editors often receive User Reports (URs) categorized as “map issue” that actually refer to problems with the route suggested by Waze to the destination.
However, editors currently have no way of knowing which destination the user entered in the app, which makes it difficult - and sometimes impossible - to properly analyze the reported issue.
I fully understand the privacy concerns involved. Still, I suggest offering users, on an optional basis, the ability to share their destination when submitting a UR, especially in cases related to “incorrect address” or “incorrect instructions.”
This would allow editors to investigate issues much more accurately and significantly increase resolution rates, without compromising user privacy, since sharing the destination would always be voluntary and contextual.
-- Português --
User Report: opção para compartilhar o destino
Com frequência, editores recebem User Reports (URs) classificados como “erro no mapa” que, na prática, se referem a problemas na rota sugerida pelo Waze até o destino final. No entanto, atualmente o editor não tem como saber qual destino o usuário inseriu no aplicativo, o que dificulta - ou até inviabiliza - a análise correta do problema reportado.
Compreendo plenamente as preocupações relacionadas à privacidade do usuário. Ainda assim, sugiro que seja oferecida ao usuário, de forma opcional, a possibilidade de compartilhar o ponto de destino ao abrir o UR, especialmente nos casos em que o problema esteja relacionado a “endereço incorreto” ou “instruções incorretas”.
Essa opção permitiria uma análise muito mais precisa por parte dos editores, aumentando significativamente a taxa de resolução dos problemas reportados, sem comprometer a privacidade, já que o compartilhamento seria sempre voluntário e contextual.
Editors often receive User Reports (URs) categorized as “map issue” that actually refer to problems with the route suggested by Waze to the destination.
However, editors currently have no way of knowing which destination the user entered in the app, which makes it difficult - and sometimes impossible - to properly analyze the reported issue.
I fully understand the privacy concerns involved. Still, I suggest offering users, on an optional basis, the ability to share their destination when submitting a UR, especially in cases related to “incorrect address” or “incorrect instructions.”
This would allow editors to investigate issues much more…
11 votes
- Don't see your idea?