This website uses cookies.
By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.
Ok, don't show again
Close
Principal differences between the publishing process on AMO and Google web stores
In case you want to use browser extensions web-stores for distribution such as AMO(addons.mozilla.org), Google Chrome Web Store, or Apple App Store, you should publish your extension and pass through the particular review process.

Even though Apple doesn't support the unified standards and holding there own requirements for building Safari extensions (Safari Applications), however, Chrome and Firefox do.

And even while using a single standard they have quite different reviewing processes and a number of significant differences in non-functional requirements. Now let's talk about these differences:

Eli Tabrisov
CTO
Remote scripts
Optional permissions
Privacy
Chrome Web Store

To facilitate the compliance of your item with the Chrome Web Store Developer Program Policies, you are required to provide the information listed below. The information provided in this form will be shared with the Chrome Web Store team. Please ensure that the information provided is accurate, as it will improve the review time of your extension and decrease the risk of this version being rejected.

You should provide justification why you need permissions and how you use it in your extension. If you mentioned one permission from a list in manifest.json file you should provide an explanations.

The list of such permissons: tabs, webRequest, webNavigation, cookies, downloads, activeTab, contentSettings, debugger, desktopCapture, geoLocation, pageCapture, privacy, proxy, sessions, tabCapture, vpnProvider, Host Permission.

Firefox Web Store

You should provide privacy policy to your add-on that details which user data is being sent and to what services. The critical things to describe in the policy are how your extension collects, uses, stores, and shares or discloses information about people. If your add-on makes it apparent to websites that it is installed, this must also be mentioned. The policy should be about the extension only, not a copy of the website's privacy policy. It should also be the actual text, as opposed to a link to a privacy policy on a website. The privacy policy can be added in the add-on settings under "Manage Authors&License" on AMO.

Also keep it in mind that any data collected by Google Analytics or any other tracking mechanism, must comply with AMO latest policy. You need to create a consent page (aka control mechanism for data collection), which is shown at install time. The consent page should contain a choice accompanied by the data collection summary. The choice to send data shouldn't be enabled by default.


Here is an example of how to create a page within the add-on https://blog.mozilla.org/addons/2016/07/15/writing-an-opt-in-ui-for-an-extension/.
Also, the summary of the data collection should be mentioned in the add-on description and privacy policy.

For more information, refer to https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy/Reviews#Data_Disclosure_Collection_and_Management


Brief summary from previous comparison tables:
Case
Chrome Web Store
Firefox Web Store
Remote scripts
Optional permissions
some limits
Privacy policy page
Privacy justification
Remote scripts
Unwanted software policy
So, it's in your own interests. That's why I recommend to trust the professionals in this matter.
Previous articles
Successful cases, development life hacks and guaranteed ways to increase user retention and profit growth.
LETS DISCUSS YOUR OPPORTUNITIES!
PLEASE, FILL IN THE FORM
Our goal is to understand your challenge and provide a solution that satisfies your expectations. This ends up in close and long term relations with our clients.
By submitting you agree with the Privacy Policy statement