Better support for intents
GMM supports many more intents than Waze, and what waze does support does not always work.
For example, Waze can handle http://maps.google.com/maps, but, Google's web maps now uses just http://maps.google.com/
And you don't handle https:// at all.
The geo:lat,lng intent seems to occasionally work. But not consistently. Didn't try geo:?q=... types of intents.
And of course, there are all sorts of country specific maps.google.* variations that aren't handled. Don't know if Android intents handle wild cards or not. It appears that GMM explicitly lists everything.
Mike Castle
shared this idea
-
VeXtreme
commented
Waze seems to ignore the "VIEW google.navigation:" intent.
(It does receive the "VIEW geo:" intent)Could you please add a receiver for "VIEW google.navigation:"?
Some apps use this over "VIEW geo:" as this directly starts the navigation in Google Maps. Where "VIEW geo:" requires a few extra click to start the navigation.I get a bit sad only seeing Maps en TomTom in the "Open with" box as I really prefer to use Waze :)
More details about this intent: https://developers.google.com/maps/documentation/android-api/intents#launch_turn-by-turn_navigation