for all clients expose an API

for Android expose:

• intents
• broadcast intents
• application shortcuts

for the slightly savvier user this allows accelerated navigation by macro (Tasker, Llama, OmniDroid, et al)

API allows for similar macro- or automation apps on iOS (ipad, iPhone), windows mobile, other platforms surely

instead of

° load waze
° click or swipe to open navigate to UI
° search for address
° select match
° go
° pick route

the macro app could accomplish this in

ONE click

this is employing merely one of a panoply of time saving waze measures

add to wiki and label unsupported should that be waze druthers

exposing more granularity would

° empower users' judgment
° conditional logic
° offload server use
° displace more Google maps/nav "sheeple"

less savvy wazers (and waze) could benefit from the efforts of the more savvy

• apply restrictions not for commercial use to kill market predatory-developers, those who spew poor code to fashion self serving malware or apps which exist primarily to render ads

the more non-commercial participants the

° better crowd value
° preferred word of mouth
° google hemorrhaging
° seize market from social gps (displace glympse et al)

add dead reckoning stir pot gently

http://waze.uservoice.com/forums/59223-client-how-can-we-improve-waze-on-your-phone-/suggestions/2360157-dead-reckoning-when-neither-data-nor-gps-available

accept GPS coordinates as destination

mix in more expansive XMPP integration for those who value communication and privacy. Use XMPP Jingle as PTT (Push To Talk)

http://waze.uservoice.com/forums/59223-client-how-can-we-improve-waze-on-your-phone-/suggestions/2997613-use-jingle-to-send-short-audio-blurbs-to-others

then waze is socially adept, privacy conscious **, open protocol embracing PLATFORM with potential for plug-in waze domain expansion

**
http://wiki.xmpp.org/web/OTR , http://otr.cypherpunks.CA

waze ought jump in both feet by implementing mpOTR

XMPP is financially wise, utterly displacing sms as many find mobile bills for smart appliances becoming unjustifiably costly (as texting over sms is often half the bill).

° retain wazers despite economic uncertainty
° niche domination
° pair with SIP SIMPLE (additional texting option), SIP presence, and SIP for conferencing while traveling [in tandem]

Jingle has video potential that would not tax waze cloud.

TL;DR It would be extremely helpful, if Waze could continuously record and store video from front facing camera.

Me and many of my friends would install a car video recorder. Main functionality is to continuously record anything that happens in front of your car, storing last few hours of recorded material.

There could be many uses for this. Mainly - helping in crashes, where you are not guilty, but you cannot prove that.

Functionality could be minimum. An option to enable or disable continuous recording through road facing camera. Setting, which indicates - how many minutes or hours of recording to keep. Easy way to extract data via iTunes. Video can be split in smaller chunks (10min max), and work like FIFO queue - when recording next 10 minutes, oldest 10 minutes chunk is removed from device.

Solution may not be trivial, but result would be greatly appreciated by many of fellow wazers.

And, yes, I know that this is not a 'quick fix' type of suggestion.

Tasker is a automation system for Android based on profiles that contains states and actions.

For instance when Tasker sees the bluetooth in my car it begins to reject most calls, reads texts aloud me, and sends a automated reply. Currently that reply just says I will get back to them when I reach my destination. Waze knows that destination and my ETA. I would like to send that in the automated texts. I would also like for Tasker to be able to tell Waze a destination. Using this info it would also be possible for Tasker to do events if the ETA changes due to traffic, like send a text to my wife telling her my new ETA for coming home from work.

You could also have a event passed to Tasker like "Arrived at destination" and then have actions based on that.

Taskers integration page is here...
http://tasker.dinglisch.net/plugins.html

A report “ride against traffic” would be:
- More easily and faster to report, despite stress.
- The other wazers know immediately what kind of danger is reporting.
- Set off the report 1.5 km / 1 mi before the action take place.

-- français --

Pour avoir vécu récemment un contre-sens, c'est frustrant de ne pas pouvoir signaler aux autres wazers un danger de ce type, assez fréquent malgré ce qu'on peut croire (1 contre-sens / semaine en France sur autoroutes, sans compter ceux qui ne sont pas détectés).
Un wazer avait indiqué un "danger sur la route" avec comme commentaire contre-sens. Mais j'ai pu voir le signalement et lire le commentaire qu'une fois à l'arrêt sur l'autoroute, à 10 voitures d'un accident mortel, résultat du contre-sens...

Un signalement dédié "contre-sens" permettrait :
- au wazer qui croise le contre-sens de pouvoir faire le signalement hyper rapidement, même dans cette situation de stress,
- aux autres wazers d'être informés immédiatement de la nature du danger,
- d'étendre le signalement à 1,5 km du lieu où il a été vu.

Please add an option to see either a birds-eye overview or a turn-by-turn list (or both?) of the route Waze is taking me on.

Sometimes I know I want to avoid a particular road. So when Waze plots a route for me at the start, I can review the proposed alternate routes and choose one. But if I need to deviate from that route to make a side errand maybe, Waze will recalculate my route on the fly, going back to its #1 preferred route. If I'm not paying close attention, this sends me back over to the road I wanted to avoid in the first place! It's hard to tell early on in a route whether Waze found a good alternate for me or if it's sending me to the toll road yet again, for example. Being able to see an overview of the entire route would allow me decide whether I should follow the navigation guidance or not.