iklimchuk
My feedback
9 results found
-
1,545 votes
AdminElla (Waze Team) (Admin, Waze) responded
-
477 votes
An error occurred while saving the comment -
38,043 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
227 votes
An error occurred while saving the comment I'd really appreciate new Polish voice with street names included
-
1,670 votes
-
1,650 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
4,026 votes
-
2,325 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
2,262 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Just imagine, you're driving and see something you want to inform other Wazers about (police trap, danger pothole or anything else). You're trying to report, type some text, send it, waiting, waiting, waiting and...it fails because of weak internet signal for example! What a frustration. "Uh-oh, try later!" Waze says...But it has no sense to try later as you've already drove away. So this important information is missed.
I see two possible solutions here:
1. Waze automatically tries to send the report later, every few minutes for example. After, let's say, 30 minutes it gives up as probably report is not valid anymore. We can establish different time outs for different events (pothole most probably wouldn't disappear in 30 mins :))
2. Just delay the report (the same as we tap "Later" button instead of Submit). So we can try to resend it manually in few minutes when network coverage will be sufficient.
i like both ways, second one should be pretty simple to implement.