This document lists requirements for applications developed with the Navigation SDK for Android.
Acceptable customer implementation use
The Navigation SDK for Android is intended for use in on-demand commercial ride and delivery services. Such services typically include (a) consumers who submit requests for a ride to a given destination or delivery of a specific item, and (b) drivers who are matched with requests and drive a vehicle to complete the services. The Navigation SDK for Android is primarily designed for providing drivers with real-time turn-by-turn navigation in a mobile application. The data generated by the API may also be used in consumer applications to share information related to driver status and for general tracking of driver locations.
The Navigation SDK for Android is not allowed for certain use cases without Google’s express prior written consent, including the following:
- Consumer navigation applications that are not tied to commercial ride and delivery services.
- Vehicle head-units or head-up display screens.
- Commercial fleet management applications that are not on-demand in nature and that involve a driver making multiple deliveries based on a pre-planned route.
- Bus services that pick up and drop off consumers at a fixed set of stops but do not keep track of the individuals who get in and out at each stop.
- Vehicle for hire ride services that allow a consumer to make unlimited stops over an extended time period that is all billed as one fee.
The Google map and logos
You must not use content provided by the Navigation SDK for Android in conjunction with a non-Google map. Unless your contract expressly permits you to do so, you must also not use content without a corresponding Google map.
You must not remove, modify, or obscure any Google logos provided as part of the Navigation SDK for Android services.
Acceptable modifications to the Navigation UI
The Navigation SDK for Android enables certain UI customizations, such as adding custom markers, changing the size and content of the header and footer surrounding the navigation viewport, or changing the size of the navigation viewport itself. In some situations, you may also want to overlay content on top of the active navigation screen. When doing so, you must not introduce modifications that inhibit safe use by drivers. For example, the following changes can negatively impact driver safety and must be avoided:
- Showing distracting animations during active navigation.
- Having overlays appear on the navigation screen without explicit driver action.
- Positioning overlays on the active navigation screen that hide the driver's current location or permanently block important navigation information, such as upcoming turns, lane guidance, compass orientation, and so forth.
Other implementation requirements
Your application must not allow drivers to input a destination for navigation.
Navigation transaction recorder implementation
Refer to the implementation guidelines for the navigation transaction recorder.