[Feature request]: expose alternative-route data + programmatic route selection (Android Auto / CarPlay can't select alternatives)

[IvelinKrastev]

Is there an existing issue for this?

• I have searched the existing issues

Use case

When RoutingOptions.alternateRoutesStrategy is all, the native NavigationView draws the alternative routes and lets the user tap one to switch the active route (firing setOnRouteChangedListener). However, the SDK exposes no way for an app to (a) read the computed alternatives, or (b) select one programmatically. This makes alternative-route selection impossible on any surface where the built-in NavigationView tap isn't available — most importantly, Android Auto (and CarPlay), whose map surface is render-only.

Proposal

Implement an API to select an alternative route on the auto screen.

[illuminati1911]

Hey @IvelinKrastev and thank you for opening the feature request. Based on my relative quick research this kind of functionality is not available on the native SDKs. As the Flutter Navigation SDK is just a wrapper around the native SDKs we cannot implement features that are not present on the native layer.'

If you have seen somewhere in the Google documentation that such feature is available on the native platforms, please let me know.

[IvelinKrastev]

Hey @illuminati1911, thank you for the response!

I wrote a FR in the Google Maps Platform's issue tracker: 521551798