Updated 2017-01-25: Thanks for the feedback given on this post. To lessen the impact of this change on developers, we’ve clarified our policy and updated this post such that it applies only to new add-ons, and those that do not … Continue reading
In 2011, we introduced the concept of “preliminary review” on AMO. Developers who wanted to list add-ons that were still being tested or were experimental in nature could opt for a more lenient review with the understanding that they would … Continue reading
Earlier I wrote an article about submitting add-ons with sources attached, which is primarily needed for obfuscated or minified add-ons. I only briefly mentioned the specific cases where attaching sources is in fact NOT recommended. If you’ve determined you do … Continue reading
With recent changes, addons.mozilla.org (AMO) now more strictly enforces our rule requiring version numbers for add-ons to be unique. Previously, the website allowed some edge cases where if a version was deleted or disabled before we reviewed it, a new … Continue reading
When submitting an add-on to addons.mozilla.org (AMO), it is sometimes necessary to attach source code in addition to the xpi file. This usually applies to add-ons with obfuscated code, because a reviewer wouldn’t be able to approve an add-on without … Continue reading
One of the advantages of listing an add-on or theme on addons.mozilla.org (AMO) is that you’ll get statistics on your add-on’s usage. These stats, which are covered by the Mozilla privacy policy, provide add-on developers with information such as the … Continue reading
If you have an active extension listing on AMO you probably got a message from us already, explaining how we will automatically sign your add-on and provide it to your users via automatic updates. The automatic signing process will run … Continue reading
Update: some of the details in the plan (particularly the timeline) have changed since this post was published. Please refer to this documentation page for the latest information. This year will bring big changes for add-on development, changes that we … Continue reading
Since we introduced the Add-on Guidelines, we’ve had a much better way to tell developers what is allowed or not for non-AMO add-ons. We also have a much clearer set of rules for blocklisting add-ons that we think don’t provide … Continue reading
Having a wide variety of content on addons.mozilla.org has always been a top priority for us, which is why some years ago we decided that we needed two different levels of acceptance for the add-ons we host and distribute. Fully … Continue reading
