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 … Read more
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 … Read more
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 … Read more
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 … Read more
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 … Read more
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 … Read more
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 … Read more
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 … Read more
We introduced the Add-on Guidelines a few months ago, setting a common bar all add-ons need to pass, regardless of whether they are hosted on AMO or not. We also … Read more