Also there would be possible to figure out algorithm of registering severe accidents for example if phone feels very hard deceleration, but user is not responding to phones questions after following stopping of car. We could warn local community that PROBABLY accident took place.
There is some merit in this one perhaps, more so on remote roads[/quote]
Again I disagree. Again you are suggesting a User have to interact with the device. And again, Waze already has a mechanism in place for it. If there is a hard stop and the User doesn't touch his phone.. Waze is going to see that the averagecspeed for that segment just dropped drastically, and create a jam. WhY does this need to prompt the User for anything OR require extra code/development/and QA time for a feature we already have.
Every single thing mentioned in this thread so far is already handled by Waze learning average speeds!
As for portholes.. come on now.. locals are going to go around them.. non-Locals will likely drive around them also if they are paying attention to the road instead of pressing even more pop ups in their nav app.
I personally vote NO for every feature that has been suggested in this thread. Waze already handles it, and the have better things to prioritize.
Sent from my Kindle Fire using Tapatalk 2