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.

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.

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

It has been noticed before that the Waze-community is divided between editors and drivers; editors being the users that earn most of their points by editing, drivers are those that earn most of their points behind the steeringwheel.

Currently, the scoreboard seems to be dominated by drivers - the topnotch of these are probably truckers, spending their live on the road, driving maybe thousands km per week, making up to 20.000 pts. There is nothing wrong with that, we NEED drivers, and I do not want to suggest that they do not earn their points.

But for editors these are hard times... you can spend, concentrated, hours per day doing all your good work for the Waze-community and still find you are outsmarted by someone who is earning his points as a sideeffect of the job he is doing - not a chance to win there, ever, because the scoreboard only shows the total of points gained by driving AND editing.

It could be an incentive for editors if there were a league for editors - that is, a scoreboard for the points gained by editing. That would make it possible to compare your editingefforts with those of other editors, rather than guessing where other users points come from.

I guess it also works the other way around, if drivers had their own scoreboard, they could compare to drivers.

And, come to think of it, there are also some points that can be gained in maintaining the forum. We could have a third league for that, too.

And ofcourse the current league should not be changed - an overall scoreboard like we have it now could still be justified.

To make competition even more fair, there could exist different leagues for countries WITH and WITHOUT a basemap, as a basemap changes the rules of the game completely.