It’s time to start checking your compatibility with 3.6 and updating your add-on if necessary. The add-on review queues are normally very busy during update times, so you should follow these guidelines to make sure your add-on stays up to date and it doesn’t have to wait too long for a review:

1. Visit Firefox 3.6 for developers and read all about the changes that have been introduced in Firefox 3.6. Some additional information for theme authors is available in this forum topic.
2. Stay up to date with Mozilla news and check http://www.mozilla.com/en-US/firefox/all-beta.html frequently for new releases.
3. Test your add-on with the beta and see if there are any compatibility problems. Most add-ons should be fine.
4. If the current version of your add-on doesn’t show any compatibility issues, you don’t need to upload a new version. Visit the Developer Hub: https://addons.mozilla.org/en-US/developers/ and change the max version value in the latest version of your add-on (it’s in the Versions and Files section). That’s all it takes. You are now able to set your compatibility to 3.6.*, which shows that no big changes are expected between beta 1 and the final release
5. If you do need to update your add-on for 3.6, submit your update as soon as possible. There will be an update rush after the final release of 3.6, and it will probably take a while for the AMO editor team to catch up.

Also, if you have binary components, some important changes have been made to the C API which might affect your add-ons. Make sure you build your add-on against the newest SDK, which is version 1.9.2. The new SDK should be available in the Gecko SDK page.

If you have any questions or comments, don’t hesitate to post here, or at the new AMO forum.

Happy coding!

PS to developers and users: you can install our band new Compatibility Reporter tool to help developers know which add-ons work on 3.6 and which don’t.

ShareThis

Before and after, there was plenty of time for socialization with the attendees and the feedback so far has been that the panel and Q&A was very informative, and we enjoyed our opportunities to talk with add-on developers one-on-one and listen to their concerns. We’re hoping to start having these meetups every other month, so make sure to join our group to be the first to know about the next one.

ShareThis

ShareThis

As an experiment in ways to get users and developers involved with this process sooner, we’ve created the Add-on Compatibility Reporter, an add-on for Firefox and Thunderbird that allows testers to report compatibility information to Mozilla.

After installing the add-on, users will be able to use any incompatible add-ons they have installed and report back to us on whether the add-ons still work like they did in previous versions or are having some issues.

Add-on developers can then browse the reports submitted for their add-ons, even if the add-on isn’t hosted on Mozilla Add-ons. We’ll also be monitoring the report submissions and emailing developers when we have information as to whether their add-on might be compatible or incompatible with an upcoming Firefox release.

So, if you’re an alpha or beta tester of Firefox or Thunderbird and want to help make sure your add-ons are compatible for the final release, grab the Add-on Compatibility Reporter now!

ShareThis

If you’re running the nightly build of Firefox 3.6- you’re in luck!  Personas support is baked in and will be a part of the final 3.6 release.  Otherwise, for those of you on Firefox 3 and 3.5, all you’ll have to do is install the Personas extension.  Once the extension is installed, you’ll be able to get live previews of personas and install them with a single click.  To learn more about Personas, including how to create your own in a few minutes, visit getpersonas.com.

ShareThis

For more information on the event, see our meetup page.

ShareThis

One of the first questions that developers want to know is whether or not they’ve picked the right contribution for their add-ons.  Let’s take a look at some charts:

In this chart, you can see a histogram of the total number of successful transactions for each amount paid.  The top 6 amounts are all $5 or under, with the notable exception of the $10 category.  Let’s take a look at the total revenue in each transaction bucket:

When we look at transactions and sort by total revenue per bucket, the story unfolds in an interesting way.  In this chart, you can see that the $10 contribution generates a majority of revenue for the measured six week period, especially when combined with the $9.99 bucket.  What this suggests is that the optimal price appears to be closer to $10 than $5, and that $10 isn’t a significant barrier for contributions.

It’s also great to know that out of 2,031 individual contributions, while 968 were for the requested amount, 742 contributions exceeded the requested amount, 159 went to add-ons with no requested amount, and only 162 were for less than the requested amount.

Of course, this isn’t a scientifically rigorous study, as the sample size is still too small for any strong conclusions, but it’s good to note that app store pricing doesn’t appear to apply to an ecosystem where all add-ons are free and paid contributions are strictly voluntary.  If a developer creates a great add-on and asks for $10, that double digit price doesn’t appear to be a barrier to donating.  In other words, add-ons users who enjoy using add-ons are also quite generous when they elect to donate contributions to those add-ons.

In future blog posts, we’ll explore the effect of employing the different mechanisms we have for letting users know about contributions.

ShareThis

Festivities start at 7 and end at 9, hope to see you there!
Edit: due to the biggest storm since 1962, we’ve postponed the event.  Stay tuned for updates regarding the new time.  Thanks.

ShareThis

These charts show me we need stronger developer outreach outside of North America & Europe. South America, for example, is a hot bed of developer talent (Brazil & Chile come to mind) and helping those developers understand the viability & power of the Mozilla platform is extremely important.

Thankfully, we’ve recently brought on Jorge Villalobos as our Developer Relations Lead. Being based in Central America (Costa Rica to be exact) will definitely allow him to increase the awareness of our tools in the surrounding countries.

A surprise from the stats was India which was 6th on the list of contributed add-ons. This is a geo we need to look at closer to see how we can build stronger developer ties there.

It was really cool to see a nice sampling on countries participating. Great motivation to keep spreading the word worldwide.

ShareThis

ShareThis