Officeload793

• An explanation of the Chrome Web Store and why you might want to use it.
• Frequently asked questions about Chrome Web Store.
• • Tutorial: Getting Started
    How to add an existing web app to the Chrome Web Store.
  • Best practices on how to implement your app and list it in the Chrome Web Store.
  • How to internationalize your Chrome Web Store app.
  • How to get the Google Account identity of a Chrome Web Store user.
• • Register as a Chrome Web Store developer
  • Publish in the Chrome Web Store
    How to publish a new extension or theme to the Chrome Web Store.
  • How to update an extension or theme ('item') that you previously published on the Chrome Web Store.
  • Guidelines for understanding why an item was rejected or removed from the Chrome Web Store and how to fix the problem.
  • Guidlines for use of Google trademarks.
  • How to share ownership of your Chrome Web Store items with other developers.
  • How to delete a developer or group publisher account on Chrome Web Store.
  • Why the payments is deprecated, details about the deprecation timeline, and more.
• • Supplying Images
    Guidelines about the kinds of images you need to supply to the Chrome Web Store.
  • How to add listing information for your Chrome Web Store item.
  • Use the privacy tab to help the Chrome Web Store team review your extension as quickly as possible.
  • Prepare to publish: set up pricing and distribution
    How to use the Pricing & Distribution tab of the Chrome Web Store dashboard to control how you charge for your Chrome Web Store item.
• • Google Chrome Web Store Developer Agreement
    The legal agreement governing the relationship between Chrome Web Store developers and the Chrome Web Store.
  • Chrome Web Store developer program policies.
  • Frequently asked questions about Chrome Web Store's spam policy.
  • Frequently asked questions about Chrome Web Store's policies on deceptive installation tactics.
  • Updated Privacy Policy & Secure Handling Requirements
    Frequently asked questions about Chrome Web Store's user data policy.
  • Google Play for Education Addendum to the Google Chrome Web Store Developer Agreement
  • Chrome Web Store complaint handling FAQ
    Frequently asked questions about the complaint handling process for the Chrome Web Store.
• • Using the Chrome Web Store Publish API
    How to programmatically create, update, and publish items in the Chrome Web Store.

Chrome Web Store Themes Background

Use the privacy tab to help the Chrome Web Store team review your extension as quickly as possible. Prepare to publish: set up pricing and distribution How to use the Pricing & Distribution tab of the Chrome Web Store dashboard to control how you charge for your Chrome Web Store item. Scopri applicazioni, giochi, estensioni e temi straordinari per Google Chrome.

Chrome Web Store

The Chrome Web Store payments system is now deprecated and will be shut down over the coming months. There are many other ways to monetize your extensions, and if you currently use Chrome Web Store payments, you'll need to migrate to one of them.

Why this is changing #

The web has come a long way in the 11 years since we launched the Chrome Web Store. Back then, we wanted to provide a way for developers to monetize their Web Store items. But in the years since, the ecosystem has grown and developers now have many payment-handling options available to them.

What it means for developers #

If you don't use Chrome Web Store payments to monetize your extension, then this does not affect you and you don't have to do anything.

If you use Chrome Web Store payments to charge for your extension or in-app purchases, you'll need to migrate to another payments processor in the near future. If you use the licensing API to keep track of who has paid, you'll need to implement another way of tracking user licenses.

Details of what's happening #

You will need to migrate your billing if you are affected by this change. Specifically, you'll need to make changes if you monetize your extensions in any of the following ways:

1. If you have configured a one-time purchase for your extension using the developer dashboard.
2. If you use any of the following resources in the Chrome Web Store API:
   • InAppProducts
   • UserLicenses
   • Payments
3. If you use the following helper methods provided by buy.js:
   • google.payments.inapp.getSkuDetails
   • google.payments.inapp.buy
   • google.payments.inapp.getPurchases
   • google.payments.inapp.consumePurchase

Milestone dates #

The deprecation timeline began with the temporary disabling of new paid items because of resource constraints due to Covid-19. We have since decided to make this change permanent, and over the coming months payments for existing items will be phased out.

Chrome Web Drivers

• March 27, 2020 Publishing of paid items temporarily disabled.
• September 21, 2020 You can no longer create new paid extensions or in-app items. This change, in effect since March 2020, is now permanent.
• December 1, 2020 Free trials are disabled. The 'Try Now' button in CWS will no longer be visible, and in-app free trials requests will result in an error.
• Feb 1, 2021 Your existing items and in-app purchases can no longer charge money with Chrome Web Store payments. You can still query license information for previously paid purchases and subscriptions. (The licensing API will accurately reflect the status of active subscriptions, but these subscriptions won't auto-renew.)
• At some future time The licensing API will no longer allow you to determine license status for your users.

After payments is disabled, you can still use the Licensing API to determine if users are currently licensed. However, this is also deprecated and will be shut down at some point, so you should begin migrating your license tracking to a different implementation.

Chrome.google.com

Exporting user licenses #

If you're using the Chrome Web Store or the Licensing API, you'll need to do the following:

• Migrate to another payments processor
• Migrate your licensing tracking

There is no way to bulk export your existing user licenses, so you need to have your users help with this part of the migration.

We recommend that you handle license migration in your back-end system, using the Chrome Web Store API. You'll need to use OAuth 2.0 with your users' consent to access these APIs. The general sequence is:

1. Implement your replacement payment/licensing scheme.
2. Prepare a license migration app that runs on your site, which accesses the Chrome Web Store API. This app needs to use OAuth 2.0 to authenticate, with user consent, and fetch the user's subscription details.
3. Create and publish a new version of your extension that directs users to your site to perform the migration.