No reason given when re-sending already accepted ZIP extension file #464
Description
I recently received a rejection notice for my submission, citing a violation of Guideline 1.1.2: "Describe your extension."
My extension was developed with strict adherence to all aspects of Guideline 1.1.2 in mind.
A detailed breakdown of how the extension complies with each key requirement of the guideline:
Compliance with Guideline 1.1.2 Breakdown:
All aspects of your extension should accurately describe the functions, features and any important limitations of your extension, including required or supported input devices. The value proposition of your extension must be clear during the first run experience. Your extension may not use a name or icon similar to that of other extensions, must not reference other browsers, and must not claim to represent a company, government body, or other entity if you don't have permission to make that representation. If screenshots are provided, they must:
- Be clear and informative.
- Render properly; for example, must not be stretched or blurry.
- All functionality of an extension should be clearly disclosed to the user. Any extension that attempts to deceive or mislead users will be removed from the store.
Accurate Description of Functions, Features, and Limitations (Including Input Devices):
The extension's store description provides a comprehensive overview of every function and feature, including step-by-step explanations and use cases.
Within the extension itself, all user interfaces include clear tooltips, labeled inputs, and contextual hints to ensure transparency.
Any limitations, such as required permissions or supported input methods (e.g., keyboard shortcuts on desktop), are explicitly disclosed in both the description and the first-run onboarding screen.
Screenshots submitted are high-resolution, non-blurry, and directly illustrate these elements without stretching or distortion.
The value proposition of your extension must be clear during the first run experience.
Clear Value Proposition During First-Run Experience:
Upon installation, users are immediately greeted with an intuitive onboarding flow that highlights the extension's core value.
Default settings are pre-configured to enable core functionality right away, allowing users to experience the benefits seamlessly without configuration hurdles. This ensures the value is evident from the first interaction, reducing any potential for confusion.
Your extension may not use a name or icon similar to that of other extensions
Unique Name and Icon (No Similarity to Other Extensions):
The extension name is original and does not mimic any existing add-ons in the Microsoft Edge Add-ons store. A search for the name or key terms yields my extension as the sole relevant result, confirming its uniqueness.
The icon is a custom design tailored to the extension's theme and does not resemble those of competitors.
must not reference other browsers, and must not claim to represent a company, government body, or other entity if you don't have permission to make that representation.
No References to Other Browsers or Unauthorized Representations:
The extension, description, and all assets make no mention of other browsers (e.g., Chrome, Firefox) to avoid any implication of cross-browser endorsement. It does not claim affiliation with, or representation of, any company, government body, or third-party entity.
All branding is original and developer-owned.
I am confident that my extension fully aligns with these guidelines and enhances the user experience in the Edge Add-ons store without misleading or deceiving anyone.
Even my extension followed ALL rules in 1.1.2 it was rejected without any detailed information of the rejection reason.