Stay organized with collections
Save and categorize content based on your preferences.
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:
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:
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.
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.
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.
Coordinate your planned launch date with the support team. All launches
follow the Google partner support launch calendars.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-10-03 UTC."],[[["\u003cp\u003eThis guide outlines the technical implementation process for partners integrating with Google's micromobility services, covering pre-implementation, feed setup, and launch approval.\u003c/p\u003e\n"],["\u003cp\u003ePartners need to prepare deep links, share brand assets, set up their GBFS feed, and ensure their apps can handle Google Maps deep links.\u003c/p\u003e\n"],["\u003cp\u003eGoogle conducts a quality assurance review before launch, focusing on feed delivery, app responsiveness, and coverage, requiring partners to provide app access and launch details.\u003c/p\u003e\n"],["\u003cp\u003eThroughout the process, partners should communicate with Micromobility Partner Support for guidance and approvals.\u003c/p\u003e\n"]]],["Partners implement in three phases: pre-implementation, feed implementation, and quality assurance. Pre-implementation involves sending deep links, logos, and icons to Google, and understanding feed specifications. Feed implementation includes making the GBFS feed accessible, sending host and authentication details, and ensuring apps support redirections from Google. Finally, partners must verify app responsiveness to feed updates and deep links, then submit app access and launch details for Google's review and approval.\n"],null,["# New provider implementation\n\nThis guide describes the typical steps required for a partner's implementation.\nThe steps are broad in description and might need to be adjusted for a given\npartner.\n| **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.\n\nPhase one: Pre-implementation\n-----------------------------\n\nSend your assets to us at Google. After we receive them, we prepare our systems\nfor the integration.\n\nPerform the following steps as part of pre-implementation:\n\n1. Follow the directions in [Format deep\n links](/micromobility/guides/deep-links#format-deep-links)\n and [Prepare default deep\n links](/micromobility/guides/deep-links#prepare-fallback-deep-links),\n including both an [iOS universal\n link](https://developer.apple.com/ios/universal-links/) and an\n [Android App\n Link](https://developer.android.com/training/app-links).\n Send both default deep links to [Micromobility partner support](mailto:micromobility-partner-support@google.com).\n\n2. Send [Micromobility partner support](mailto:micromobility-partner-support@google.com) your bike-sharing logo and vehicle icons. For more\n information, refer to [Icon\n specification](/micromobility/guides/brand-and-images#icon-specification).\n\n3. To become familiar with how feeds are constructed and delivered, refer to\n the specifications in the [Reference](/micromobility/reference/introduction)\n tab and [Guidelines for feed\n delivery](/micromobility/guides/guidelines-for-feed-delivery). Direct\n questions about these guides to [Micromobility partner support](mailto:micromobility-partner-support@google.com).\n\n4. For a list of recommended capabilities to be supported in the native\n application, refer to [Supported\n capabilities](/micromobility/guides/supported-capabilities).\n\nPhase two: Feed implementation, delivery, and tests\n---------------------------------------------------\n\nAfter you've generated your General Bikeshare Feed Specification (GBFS) feed,\nperform the following steps to implement, deliver, and test it:\n\n1. To make your GBFS feed available to Google, refer to [Guidelines for feed\n delivery](/micromobility/guides/guidelines-for-feed-delivery).\n For information on how to build your GBFS feed, refer to the specifications\n in the [Reference](/micromobility/reference/introduction) tab.\n\n2. Send [Micromobility partner support](mailto:micromobility-partner-support@google.com) the details for the host address and authentication\n methods.\n\n3. After your feed is available on our servers, Google verifies your coverage,\n feed delivery times, and deep links.\n\n4. Update your iOS and Android apps to support redirections that come from GMM.\n Your apps must be able to do the following:\n\n - Respond appropriately if a Micromobility request comes from a GMM deep\n link.\n\n - Support the custom URL schemes as part of the pre-implementation\n phase, in addition to the individual deep links the GBFS feed provides.\n\nPhase three: Quality assurance and technical launch approval\n------------------------------------------------------------\n\nPrior to the quality assurance (QA) review and technical launch approval, verify\nthe following:\n\n- Your apps are ready to provide feed updates to Google every 30 seconds with latency that doesn't exceed 30 seconds.\n- Your apps respond to GMM deep links.\n\nTo submit your app for QA and launch approval, perform the following steps:\n\n1. Notify [Micromobility partner support](mailto:micromobility-partner-support@google.com) and provide them with the following:\n\n - Access to your apps. If they're not yet published, send a TestFlight\n invite for your iOS apps and the APK file for your Android apps.\n\n - Instructions to access your app outside of your operation countries if\n any special steps are necessary.\n\n - A test account for your apps, if necessary.\n\n - The countries you're ready to launch in.\n\n2. Wait for notification that the support team has completed their review. The\n support team checks your feed's coverage and validates your app integration\n with GMM. Google tests how the apps respond to the integration but this\n process doesn't actually unlock any bikes.\n\n3. Coordinate your planned launch date with the support team. All launches\n follow the Google partner support launch calendars."]]