Addon signing for private/personal add-ons

Hello,

I coded a small Firefox extension called SmartFill to learn JavaScript and Firefox extension development. I was rather disappointed about the programming platform, how difficult it was to get it approved and how little feedback it created, only one rating. I decided then to give up making a public add-on because writing a private add-on for personal use is much easier, maybe only half of the work or even less. Is this a problem with the new signing policy? What does it mean for me?

If you intend to use it in a release or beta version then in the future you will need it either to be signed, or use the yet to come unbranded Firefox. If you want it signed you’d need to put it through AMO as an unlisted addon. There it only needs to pass an automated review, unless it gets warnings, where it will need to be manually reviewed.

1 Like

I appreciate the difficult approval process. It makes me feel safe knowing that other addon devs went through that too. So now I feel comfortable installing any addon out there, that its free of malware.

1 Like