PapaMarc
My feedback
2 results found
-
4 votes
An error occurred while saving the comment PapaMarc
supported this idea
·
-
15 votes
An error occurred while saving the comment PapaMarc
commented
well, it's >10yrs after the initial post, so i'm not overly confident that anyone will ever read this on the engineering team... but yes, would be great if as i zoom in, the text didn't stay the same overly small size but rather enlarged so i could read a given street name i want to see in detail...
for a variety of reasons (i'll enumerate a few scenarios) a small delete UI element eg. 'x' at the top right of the 'add(itional/ed) stop' box would be highly useful...
1) I often will add a stop on a regular route i take. The reason i add the stop is because the default route Waze gives me does not take the exit/interchange i prefer, and Waze does not 'learn' my preferred route over time. But i always want to take this exit which is not offered to me. So that i don't miss the exit, i add a location just off this exit (which sometimes i go to, and sometimes i don't as it's just beyond the next road i want to get on). So... once i get off the exit, if i just get on my next road Waze harrasses me endlessly to turn around to attempt to get me back to the 'stop' on the route.
Yes-- i can delete the entire route and reselect my original intended destination, but i'd rather just delete the stop, and continue on my way.
2) sometimes i 'add stop' multiple times iteratively, as a way of seeing which of the restaurants offered, or gas stations offered, are REALLY on my ongoing route. While it's nice that Waze offers the ability to see nearby 'xyz', it doesn't do a great job of clarifying which are actually upcoming on the ongoing route (v. requiring one to backtrack... particularly meaningful on some interstates w/exits ever 30mi or so). So to verify which one of several works best i often want to add a stop, and then remove it, iteratively.
3) this further is related to design issues with 'saved places' and 'searches for them' which only at present return 2 results-- so the 'workaround/scenario' of keeping a list of previously found spots like 'restaurants/gas' and iteratively seeing if they're upcoming as a way of finding them in a timely/orderly manner is hindered at present on multiple dimensions. Though could be fixed quite easily, by a) allowing 'delete of an added stop' and b) fixing 'search of saved' places to return all in the user's saved list v. only 2.
see: https://www.waze.com/discuss/t/save-location-not-persisting/365962/8 for further information regarding limitations of 'saved' locations.
thanks in advance for your consideration!