In order to streamline the app discovery experience for users and to facilitate Drive app publication, we are phasing out publication of Drive apps to the Chrome Web Store. Once this process is completed, the G Suite Marketplace will be the store for Drive apps; Chrome extensions will continue to be presented in the Chrome Web Store and are unaffected by this change.
To prepare for this shift, all Drive apps must have a G Suite Marketplace listing prior to January 25, 2019. In the short term, Drive apps will be listed in both the Chrome Web Store and the G Suite Marketplace, but sometime after January 25, 2019, the Chrome Web Store listings will be removed. Once this phase out is complete, the G Suite Marketplace will handle all Drive app listings, for both users and domain administrators.
This guide provides information about this migration, and explains the steps you need to take (if any) to ensure your apps are listed properly in the G Suite Marketplace.
What you need to do
Read the following sections to determine what publishing or migration actions are required, if any.
- If your Drive app isn't published yet, publish it to both the Chrome Web Store and G Suite Marketplace. Sometime after January 25, 2019 these instructions will be revised again to only describe publication to the G Suite Marketplace.
- If your Drive app was published and is currently listed to the Chrome Web Store, create a new G Suite Marketplace listing for it.
Create a new G Suite Marketplace listing for a Chrome Web Store app
If your Drive app was published and is currently listed to the Chrome Web Store, you must take a few steps to create a new G Suite Marketplace listing.
- Review the required assets for G Suite Marketplace listings and make sure you have these assets for your Drive app. These assets are used to define the appearance and content of your app's G Suite Marketplace listing. Since the original Chrome Web Store app listing uses some of these assets, you can simply provide the same asset again.
- Publish your app with the G Suite Marketplace SDK. This requires you to enable the G Suite Marketplace SDK in your app's Cloud Platform project and then configure the SDK.
This section provides answers to some common questions about this migration.
What happens if I don't or can't add a G Suite Marketplace listing to my Drive app by the deadline?
At some point on or after the January 25, 2019 deadline, your app listing will be removed from the Chrome Web Store. When that happens, new users will be unable to find or install the Drive app. Users that have already installed the app can continue using it, but if they ever uninstall the app they won't be able to re-install it again.
Is the Chrome Web Store being shut down?
No. The Chrome Web Store is simply not the best place to showcase Drive apps, and it is better to have app listings in one location so that users and domain administrators can find them more easily.
If my Drive app is privately published/visible, do I need to migrate?
Does migration require my Drive app to be reviewed by Google?
In most cases apps previously published to the Chrome Web Store can be migrated automatically without manual review. However, if you make updates to your Drive app code that change its authorization scopes, an additional review may be required when you republish in the G Suite Marketplace.
If you are publishing your app for the first time to the G Suite Marketplace, a review by Google is required. The review process confirms that published apps meet Google's design, content, and style guidelines and provide a good user experience.
How does migration to the G Suite Marketplace affect my Drive app user installs, user ratings, and user reviews?
If the app was previously published in Chrome Web Store, then its user installs, reviews, comments, and star ratings will be migrated to the new G Suite Marketplace listing. Since user installs are migrated, your existing app users can continue using the app without interruption.