Changes prompted by Firefox after the add-on is installed do not require an additional opt-in. The features must be “opt-in”, meaning the user has to take non-default action to enact the change.The add-on description must clearly state any changes made by these features.This includes features that impact user privacy or security, make unexpected changes to web content, change default settings like the new tab page, homepage, or search engine, or are not related to the add-on’s core function(s).Īny “unexpected” feature(s) must adhere to all of the following requirements: “Unexpected” features are those that are unrelated to the add-on’s primary function, and are not intuitive from the add-on name or description. Please consult our best practices guide for creating an appealing listing. The add-on should have an easy-to-read description about everything it does, and any information it collects. Users should be able to easily discern what the functionality of your add-on is and should not be presented with unexpected user experiences after installing it.
Removing your extension from distribution.Will I ever be able to sell through AMO?.Use plain language in any privacy policy or license agreement.Select the right platforms and versions.The add-on description can be longer, but not too long.Focus on key features in your screenshots.Make sure your summary is just long enough.
0 kommentar(er)
