# 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.

> [!NOTE]
> **Note:** Some of the phases and steps can overlap. For example, it's possible to implement your feeds before you send Google your product icons. This guide doesn't take into account any business, contract, or public relation coordination for your service. It only covers the technical implementation.

## 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. Follow the directions in [Format deep
   links](https://developers.google.com/micromobility/guides/deep-links#format-deep-links)
   and [Prepare default deep
   links](https://developers.google.com/micromobility/guides/deep-links#prepare-fallback-deep-links),
   including both an [iOS universal
   link](https://developer.apple.com/ios/universal-links/) and an
   [Android App
   Link](https://developer.android.com/training/app-links).
   Send both default deep links to [Micromobility partner support](mailto:micromobility-partner-support@google.com).

2. Send [Micromobility partner support](mailto:micromobility-partner-support@google.com) your bike-sharing logo and vehicle icons. For more
   information, refer to [Icon
   specification](https://developers.google.com/micromobility/guides/brand-and-images#icon-specification).

3. To become familiar with how feeds are constructed and delivered, refer to
   the specifications in the [Reference](https://developers.google.com/micromobility/reference/introduction)
   tab and [Guidelines for feed
   delivery](https://developers.google.com/micromobility/guides/guidelines-for-feed-delivery). Direct
   questions about these guides to [Micromobility partner support](mailto:micromobility-partner-support@google.com).

4. For a list of recommended capabilities to be supported in the native
   application, refer to [Supported
   capabilities](https://developers.google.com/micromobility/guides/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](https://developers.google.com/micromobility/guides/guidelines-for-feed-delivery).
   For information on how to build your GBFS feed, refer to the specifications
   in the [Reference](https://developers.google.com/micromobility/reference/introduction) tab.

2. Send [Micromobility partner support](mailto:micromobility-partner-support@google.com) 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](mailto:micromobility-partner-support@google.com) 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
   follow the Google partner support launch calendars.