Hey all,
Wanted to discuss an idea; we’ve been trying to get our firefox addon into the store for a pretty long time now (our first attempt was in april of 2015.) We just resubmitted again, and in order to make the process go more easily, we’ve uploaded a version with all of the sources un-minified by our build process and have included a spreadsheet with references to all of the sources used, so fingers crossed.
However, it seems to me like larger addons like ours (which are extensions of larger products) are pretty prone to these sorts of issues, and the feedback cycle takes a really long time to work through. Has there been any consideration for a different review process for larger addons, especially ones that are connected with a business?
Some of the requirements aren’t practical for us; we want to be able to uglify all of the sources in our build pipeline, but that’s an insta-fail because the sources would then be obfuscated and not match your checksums. We’re also a security company, so we take extra strides to make sure data is being handled properly—if we were truly a risk we’d not need to have a modified 3rd party library to gain access to sensitive data.
I can imagine the work needed to verify our gigantic addon is a lot more than the usual addon, and it’s also valuable for us to have this live, so I’d even be willing to pay for a ‘addon buddy’ to help us work through the submission and get it ready to go live. I could also see something of an interview type process to quickly get the review team acclimated with the addon to make review easier.
To be clear I’m not suggesting that this is purchasing an approval, but something to justify the extra cost we’re putting on the system to review a super large addon.
Would be very curious to hear if that option has been discussed before—it seems totally fair from my perspective, and I’d love to get our addon up before the 1 year mark rolls around .