Google Navigation for Flutter and React Native quick reference

Open source plugins that add a Google Navigation widget to Flutter apps and a Google Navigation component to React Native apps that target Android and iOS. They require a project with billing, an API key, and the Navigation SDK for Android and Navigation SDK for iOS enabled.

Google Navigation for Flutter and React Native: key facts

  • Product: Google Navigation for Flutter and React Native
  • Also known as: Google Navigation for Flutter, Google Navigation for React Native, Google Navigation plugins for Flutter and React Native
  • Category: Routes
  • Platform: Cross-platform (Flutter and React Native)
  • Runs on: Client (app or browser code)
  • Launch stage: GA
  • Lifecycle: Active
  • Overview: Google Navigation for Flutter and React Native overview

Google Navigation for Flutter and React Native: when to use it

Use Google Navigation for Flutter and React Native when:

  • You need turn-by-turn Google Navigation in a Flutter app that targets Android and iOS.
  • You need turn-by-turn Google Navigation in a React Native app that targets Android and iOS.
  • You want one Flutter or React Native codebase that adds Google Navigation to both Android and iOS apps.

Don't use Google Navigation for Flutter and React Native when:

  • You build a native Android app and need Technical Support Services and Deprecation Policy coverage for the navigation code. Use Navigation SDK for Android instead.
  • You build a native iOS app and need Technical Support Services and Deprecation Policy coverage for the navigation code. Use Navigation SDK for iOS instead.

Google Navigation for Flutter and React Native: setup

Official Google Navigation for Flutter and React Native packages:

  • pub: google_navigation_flutter
  • npm: @googlemaps/react-native-navigation-sdk

Google Navigation for Flutter and React Native: common mistakes

  • Problem: The plugins are in version 0.x, so backwards-incompatible changes can appear in any release. Fix: Pin the plugin version, and check the changelog on the package page (pub.dev or npm) for breaking changes before you upgrade. See /maps/documentation/cross-platform/navigation.
  • Problem: The plugins aren't a Google Maps Platform Core Service, so Technical Support Services, the SLA, and the Deprecation Policy don't cover the plugin code. Fix: File bugs and feature requests as GitHub issues in the plugin repository and ask questions in the developer community channels. See /maps/documentation/cross-platform/navigation.
  • Problem: The plugins need the Navigation SDK for Android and Navigation SDK for iOS enabled on a billing-enabled project with an API key. Fix: Enable the Navigation SDK (navigationsdk.googleapis.com) in a billing-enabled Cloud project and create an API key before you use the plugins. The one service covers both Android and iOS. See /maps/documentation/cross-platform/navigation.