New provider implementation

This guide describes the typical steps required for a partner's implementation. The steps are broad in description and might need to be adjusted for a given partner.

Phase one: Pre-implementation

Send your assets to us at Google. After we receive them, we prepare our systems for the integration.

Perform the following steps as part of pre-implementation:

  1. To create custom URL schemes for Google to use as both a fallback link as well as an app detection link, refer to the Prepare fallback deep link section. Email the custom URL schemes to Micromobility partner support and add them to the feed.

  2. Send Micromobility partner support a download link for the rental Android app and/or iOS app and include it in the feed. The link must follow Android and iOS best practices. The viewing app must open directly to the URI of the native app store app instead of a website or intermediary landing page.

  3. Send Micromobility partner support your bike-sharing logo and vehicle icons. For more information, refer to Icon specification.

  4. To become familiar with how feeds are constructed and delivered, refer to the specifications in the Reference tab and Guidelines for feed delivery. Direct questions about these guides to Micromobility partner support.

  5. For a list of recommended capabilities to be supported in the native application, refer to Supported capabilities.

Phase two: Feed implementation, delivery, and tests

After you've generated your General Bikeshare Feed Specification (GBFS) feed, perform the following steps to implement, deliver, and test it:

  1. To make your GBFS feed available to Google, refer to Guidelines for feed delivery. For information on how to build your GBFS feed, refer to the specifications in the Reference tab.

  2. Send Micromobility partner support the details for the host address and authentication methods.

  3. After your feed is available on our servers, Google verifies your coverage, feed delivery times, and deep links.

  4. Update your iOS and Android apps to support redirections that come from GMM. Your apps must be able to do the following:

    • Respond appropriately if a Micromobility request comes from a GMM deep link.

    • Support the custom URL schemes as part of the pre-implementation phase, in addition to the individual deep links the GBFS feed provides.

Phase three: Quality assurance and technical launch approval

Prior to the quality assurance (QA) review and technical launch approval, verify the following:

  • Your apps are ready to provide feed updates to Google every 30 seconds with latency that doesn't exceed 30 seconds.
  • Your apps respond to GMM deep links.

To submit your app for QA and launch approval, perform the following steps:

  1. Notify Micromobility partner support and provide them with the following:

    • Access to your apps. If they're not yet published, send a TestFlight invite for your iOS apps and the APK file for your Android apps.

    • Instructions to access your app outside of your operation countries if any special steps are necessary.

    • A test account for your apps, if necessary.

    • The countries you're ready to launch in.

  2. Wait for notification that the support team has completed their review. The support team checks your feed's coverage and validates your app integration with GMM. Google tests how the apps respond to the integration but this process doesn't actually unlock any bikes.

  3. Coordinate your planned launch date with the support team. All launches are subject to the Google partner support launch calendars.