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 ~
20946 results found
-
Outlines for “area” place types (App/Livemap)
Currently, polygons representing “area” place types in the app and in Livemap are rendered in an overly simplified way, using a uniform fill with no visible outlines. This design choice reduces visual clarity when distinguishing between adjacent areas. In cases where one area is located inside another, the label of the inner area appears to “float” over the outer one, with no clear indication of its limits.
However, there are legitimate scenarios in which representing buildings or facilities as areas within a larger, usually enclosed area is both correct and necessary — especially in complex urban environments such as universities, airports, administrative centers, and similar locations.
It is also worth noting that this limitation does not apply to green areas (nor to police areas, which are rendered in red on Livemap), which can coexist within regular areas without causing the same visual conflicts.
Given this, I propose that Waze restore the display of subtle visual outlines for “area” place types. This simple change would improve map readability and better align the use of area places with real-world mapping needs.
-- Português --
App/livemap: bordas para locais do tipo "área"
Atualmente, os polígonos que representam locais do tipo “área” no app e no Livemap são renderizados de forma excessivamente simplificada: seu preenchimento é uniforme, sem bordas. Essa opção de design compromete a legibilidade da separação visual entre áreas contíguas. No caso de áreas dentro de outras áreas, o rótulo textual da área menor passa a “flutuar” sobre a maior, sem distinção de limites.
Todavia, há cenários legítimos nos quais seria correta e necessária a representação de edificações dentro de uma área maior, geralmente cercada, especialmente em ambientes urbanos complexos (universidades, aeroportos, centros administrativos etc.).
Vale observar que essa limitação não se aplica às áreas verdes (nem às áreas policiais, que são vermelhas no Livemap), que podem coexistir dentro de áreas comuns sem gerar os mesmos conflitos visuais.
Diante disso, proponho que o Waze restabeleça a exibição de bordas visuais, ainda que sutis, para os locais do tipo “área”. Essa simples mudança alinharia melhor o uso desse tipo de local às necessidades reais de mapeamento.
Currently, polygons representing “area” place types in the app and in Livemap are rendered in an overly simplified way, using a uniform fill with no visible outlines. This design choice reduces visual clarity when distinguishing between adjacent areas. In cases where one area is located inside another, the label of the inner area appears to “float” over the outer one, with no clear indication of its limits.
However, there are legitimate scenarios in which representing buildings or facilities as areas within a larger, usually enclosed area is both correct and necessary — especially in complex urban environments such as universities,…
10 votes -
Add support for Qobuz music player
Add support for Qobuz music player
https://apps.apple.com/us/app/qobuz-music-editorial/id946429340
10 votes -
Add more stops would be nice
There is no option to add multiple stops, it would be really nice to have this feature on my navigation. In this way, I won't need to switch to other maps app
10 votes -
change speed bump to traffic calming device
There are many different devices used to slow vehicles other than speed bumps. Other examples include chicanes, roundabouts, splitter islands, entrance treatment, speed pillows, speed humps and intersection humps. I'm sure there are others too.
The speed bump permanent hazard would fit all of these other types of methods used to slow vehicles down but if we add a speed bump where there technically isn't a speed bump we confuse the wazer and likely will generate unnecessary URs.
If we changed the name from speed bump to 'traffic calming device' (my suggestion), we easily fit all these slow-down methods and alert with a simple and clear message to the wazer that speed control measures are in effect ahead.
Instead of creating a unique permanent hazard for each of these devices, I instead suggest we broaden the definition the one we already have and change it's name accordingly.
I'm currently working with the city of Sandy Springs, Ga and they employ all of the devices I've mentioned here but I am hesitant to add "speed bump" PH to their chicanes and other devices which are specifically not speed bumps.
There are many different devices used to slow vehicles other than speed bumps. Other examples include chicanes, roundabouts, splitter islands, entrance treatment, speed pillows, speed humps and intersection humps. I'm sure there are others too.
The speed bump permanent hazard would fit all of these other types of methods used to slow vehicles down but if we add a speed bump where there technically isn't a speed bump we confuse the wazer and likely will generate unnecessary URs.
If we changed the name from speed bump to 'traffic calming device' (my suggestion), we easily fit all these slow-down methods and…
10 votes -
Delete the Stop point and continue navigating to final destination
Unfortunately, it is not possible to remove the intermediate point on the route after adding it.
This feature is very much needed.
10 votes -
Train Blocking Roads
Waze users need to be able to report if a train is blocking a road. I am a school principal and students are late to school because parents have no way of seeing if a road is blocked by a train until they pull up to it.
10 votes -
Enable Speech-to-Text for Map Update Requests While Driving (via Android Auto and CarPlay)
I would like to suggest an improvement to Waze that would allow users to fill out map update requests (URs) using speech-to-text while driving, particularly when connected through Android Auto or CarPlay.
Currently, when users select a map update option (such as "Incorrect address," "Missing road," or "Speed limit") while driving, there is no way to add a description of the issue. This limits the ability to provide detailed reports and often results in incomplete information being submitted. With speech-to-text functionality, users could quickly and safely dictate descriptions of the problem without having to stop or manually type anything.
For example:
General error: "There’s a detour due to roadwork on Main Street."
Missing road: "There’s a road missing between Maple Ave and Pine St."
Speed limit: "The speed limit is 60 on Highway 10, not 45."
Incorrect address: "The address for 123 Oak St should be 125 Oak St."
This feature would not only make reporting map issues easier and more detailed, but it would also ensure that users can submit accurate information safely while driving. By integrating speech-to-text, Waze could enhance its mapping accuracy without distracting drivers from the road.
I would like to suggest an improvement to Waze that would allow users to fill out map update requests (URs) using speech-to-text while driving, particularly when connected through Android Auto or CarPlay.
Currently, when users select a map update option (such as "Incorrect address," "Missing road," or "Speed limit") while driving, there is no way to add a description of the issue. This limits the ability to provide detailed reports and often results in incomplete information being submitted. With speech-to-text functionality, users could quickly and safely dictate descriptions of the problem without having to stop or manually type anything.
For…
10 votes -
Additional fields in Tollbooth hazard
It would be great to add some fields to Tollbooth hazard like "name", "price" and "payment methods", so that Waze can warn (on screen and TTS) about the next toll on the Wazer route and, at least, its name and price.
10 votes -
Gulf of America doesn't exist. Change it back to Gulf of Mexico
The rest of the world calls it the Gulf of Mexico. It's been the Gulf of Mexico long before the USA came into existence.
10 votes -
I suggest making the app works with offline maps.
It’s very useful to make the app working without internet by adding the ability to load offline maps.
Thanks.10 votes -
Convoy option
Be able to join a convoy with friends/family set a destination and everyone that is in the convoy can see the navigations and see what everyone’s ETA and where they are on the map
10 votes -
Bug RoundAbout exit during driving : A U-turn is always showing on the dashboard of the car
The dashboard of the car always shows an U-turn exit for all roundabout on android auto.
It will be good to replicate, like the application Google Maps does, the correct information seen on the map to the dashboard car.
Because actually for all roundabout, Waze shows on the dashboard a u-turn whereas the exit number and indication are correct on the map.
Suggestion to the forum : A picture to upload would help to explain more than a long explanation.
10 votes -
More UK Voices WITH STREET NAMES
Please give some more options of voices that include street names with differnt UK accents. There are so many variations of accent in the UK and having some more options that still include street names would be amazing! I used to love Kates voice but the new one is so much worse. Please create some more UK voice options!!
10 votes -
Pouvez vous activer le mode picture in picture sur android
Pouvez vous activer le mode picture in picture sur android?
10 votes -
Change the speed camera icon
The speed camera icon has recently changed to a new one however it blends in too much so I can be very misleading, the old speed camera icon was fine and was very noticeable compared to everything else (especially when you have a route inputted in)
10 votes -
Voz do MC Fioti
Voltar com a voz do MC Fioti (brasileiro). Era a melhor voz do waze. Aliás depois de andar com algumas pessoas no meu carro, essas mudaram para a voz do MC Fioti, porque gostaram muito.
10 votes -
Change "Saved" places from 100 to unlimited
Changed the visible Saved places to unlimited instead on 100.
10 votes -
Exit Waze when disconnecting from Apple CarPlay
I love Waze for longer journeys, using it with Apple CarPlay. But I don't need it for popping to the shops - i.e. most daily journeys.
However the App starts up on my phone every time I get in the car regardless, and then continues running even after I get out. It really drains my phone battery. I have to remember to close it manually. I can't find a way to stop this behaviour - it is a real pain.
I'm sure it wasn't always like this, but this means I have had to disable Waze on my CarPlay setup.
I would like to be able to configure Waze so it automatically closes when I disconnect from Apple CarPlay.
I love Waze for longer journeys, using it with Apple CarPlay. But I don't need it for popping to the shops - i.e. most daily journeys.
However the App starts up on my phone every time I get in the car regardless, and then continues running even after I get out. It really drains my phone battery. I have to remember to close it manually. I can't find a way to stop this behaviour - it is a real pain.
I'm sure it wasn't always like this, but this means I have had to disable Waze on my CarPlay setup.
…
10 votes -
Floating window on exit
Would like Waze to implement "floating" window on exit. Or atleast have pop up notification of the next direction, like Google maps has. When I close out Waze, I have no way of knowing the next step unless I reopen app.
10 votes -
Seperate speed limit warning for each vehicle type
Hi Waze team,
I have used Waze while driving motorcycle. But in my opinion, it would be good if we can separate the speed limit for each vehicle type because the speed limit may be different with cars on some roads. Maybe it's a good development route for supporting another type of vehicle like truck for example10 votes
- Don't see your idea?