Google Chrome Web Store Updates

  • Thread starter Thread starter Sushubh
  • Start date Start date
  • Replies Replies 23
  • Views Views 6,426
Dear Developer,

The Chrome Web Store is introducing updates to our policies for extensions using MV3. These updates expand the possibilities to load remote content within your extension, while remaining in compliance with our remotely hosted code policies. Here is a guide on the changes and what they mean for your extension development:

1. Self-Contained Functionality: A Focus on Transparency

The core principle remains: the full functionality of your extension should be easily discernible from the submitted code. It is critical to ensure that the logic driving your extension is well-defined within its codebase.

2. External Resource Usage: Striking a Balance

Extensions can still reference and load data from external sources, but these resources must not contain any logic. Extensions are permitted to execute logic from remote sources only through documented APIs like the Debugger API and User Scripts API. This strikes a balance between flexibility and security, allowing external data without compromising the transparent nature of your extension's functionality.

3. Isolated Contexts: Exemptions and Responsibilities

Code running in isolated contexts, such as iframes and sandboxed pages, is exempt from certain restrictions on loading code from remote sources. However, it's crucial to maintain transparency. The full functionality of your extension should still be discernible in these contexts.

4. Review Process Consequences: A Note on Enforcement

If we are unable to determine the full functionality of your extension during the review process, we may take appropriate action. Submissions that lack clarity or violate policies might be rejected or removed from the Chrome Web Store.

You can learn more about today’s guidance in our Program Policies. These policy clarifications will go into effect on April 15, 2024. After that date, extensions in violation of these new policies may be removed from the Chrome Web Store and be disabled.

If you have any questions, you can contact developer support.

Thank you for your cooperation, and for your participation in the Chrome extension ecosystem!

- The Google Chrome Web Store team
 
Dear Developer,

We are announcing a series of updates to our Developer Program Policies page designed to encourage the development of high quality products, prevent deceptive behavior, and ensure informed user consent. These updates include:

Listing Requirements
Consistency and transparency are paramount to maintaining user trust and satisfaction, and one of our key priorities is to maintain accurate and functional listings on the Chrome Web Store. Our policy has always required certain parts of your listing to be up to date, such as your product’s description. Moving forward, all elements within a product listing must be up to date and fully operational. This change addresses common issues such as broken videos and non-functional elements that users might encounter on a product's listing page.

Additionally, it is crucial that the behavior of your extension matches the descriptions provided both in the product listing and in the developer dashboard.

Quality Guidelines
We are clarifying our Quality Guidelines to ensure a seamless user experience. Specifically, new tab page extensions are now explicitly prohibited from altering a user's search experience unless they use the chrome.search API. This clarification aims to prevent any unexpected or unwanted changes to a user’s browsing experience, ensuring that any modifications are clearly communicated and controlled.

For more information on the Quality Guidelines policy, see our updated FAQ.

Deceptive Installation Tactics
To further protect our users, we are updating our policies regarding deceptive installation tactics. This update specifies that all advertisements, marketing materials, and referral pages fall within the scope of our policies. Additionally, every call-to-action button must clearly state that an extension is being installed. This requirement is designed to eliminate any ambiguity, ensuring users are fully aware when they are installing an extension.

For more information on the Deceptive Installation Tactics policy, see our updated FAQ.

What This Means For You
As developers, it’s essential to review and align your extensions with these updated policies. Extensions which do not meet these new requirements by September 9, 2024 will risk being removed from the Chrome Web Store.

Here’s what you can do to comply:

Audit Your Listings:
Check all elements of your product listings to ensure they are current and fully functional. Verify that your extension’s behavior is accurately described and consistent across all platforms.

Review New Tab Extensions:
If you develop new tab page extensions, ensure they comply with the updated guidelines and use the chrome.search API appropriately.

Update Installation Processes:
Update your ads, marketing materials, and referral pages to clearly indicate when an extension is being installed. Make sure all call-to-action buttons explicitly state this to avoid any deceptive practices.

Thank you for your attention to these important updates. We’re grateful for all you’ve done to build for the Chrome Web Store, and we’re here to help you navigate the changes as we continue to make it even better. We’re excited about what lies ahead, and as always, we welcome your feedback.

For more details, please visit our Developer Policies page.

- The Google Chrome Web Store team

 

Back