Skip navigation

Sorry for the long absence! It’s been a busy past few days, especially since I had a flight at 6am yesterday morning to Vancouver. Mozilla is throwing its summit in Whistler this year, and it started yesterday and ends tomorrow. On Tuesday we were treated to a luxurious reception dinner replete with seafood and Canadian beer, along with free shirts and the like. And then after that…well, that’s probably not appropriate for a blog post. (Hooray for not being underage in Canada!)

Yesterday began with a series of keynotes and demos from the likes of Mitchell Baker and Jay Sullivan. The demos of Firefox 4 were, in the tersest of forms, extraordinary and mind-blowing. They boasted TabCandy and application tabs, along with rapidly quickened JavaScript rendering (especially in relation to Chrome) and the capabilities of WebGL for 3D graphic rendering. Perhaps the most impressive demo was the five-minute, ad hoc creation of a text translation API that took a grand total of fifteen lines of code.

The rest of the day certainly didn’t disappoint. The day was divided into three breakout sessions; for each session slot, we had to pick from a whole list of diverse choices. The decisions were difficult. My first breakout session discussed the cultural implications of messaging and how messaging can be incorporated into the Mozilla message. Many of you are probably familiar with the Mozilla manifesto and thus recognize the ideological differences that separate us from our competitors in the open web. We discussed the advantages of desktop-based messaging clients and the importance of aligning our interests with those of the user. In response to this need, we talked about prototypes of UI’s and new add-ons for Thunderbird and Raindrop (a web-based email client ala Gmail that is flexible and dynamic).

About an hour later, I headed to my second breakout session, which talked about product marketing for Firefox: how to “keep Firefox sexy.” In light of growing browser competition and the recent release of beta 1 for Firefox 4, market position is key, especially as product differentiation has become scarce. As the speakers noted in the presentation, it’s not about beating the competition; it’s about positioning them. Thus devising taglines and branding for Firefox 4 has been a long and arduous process.

The final breakout session discussed the unification of the Mozilla web universe. Mozilla has so many resources online that are largely disconnected to each other. As a result, branding Mozilla is difficult and accessing its resources in a simple, convenient way is even more so. To address this problem, several Mozillians talked for about an hour and a half or so devising brain maps and diagrams to configure potential layouts of Mozilla’s web universe. Be on the lookout soon for layout changes! The call to action at the session was powerful and will surely be a priority for Mozilla’s engagement team in the near future.

Afterward we went to dinner at Bavaria, a ridiculously awesome (and expensive!) fondue restaurant. Thanks again to Mozilla for paying for all of it!

Stay tuned for updates on day 2!


If you’re interested in learning about the changes we’re making to the Mozilla Developer Network and our efforts to engage and communicate with developers, check out the talk I’m giving with Jay Patel at 1:30pm PST. The viewing information is as follows:

  • Wednesday, June 30th 2010 @ 1:30pm
  • Mozilla HQ in Ten Forward and via Air Mozilla
  • Dial-in info for those that want to call in: 1-800-707-2533 (password 369) or 1-650-215-1282 (extension 92#)….then dial Conference number 8600#

It’ll be a good time. See you then!

EDIT: You can find a copy of the slide deck here.

(This entry was written in collaboration with Jay Patel. Note that this is the same entry as the one found on Mozilla Hacks.)

To follow up on the developer survey from last November, we did a second survey this past March after the releases of Firefox 3.6 and Firebug 1.5 to gauge developer reactions to the latest features in the browser and a much improved version of everyone’s favorite developer tool.

In this post we’ll share the results of our latest survey and provide some data and insights from all the great feedback we have received. We hope this will help us better understand developers’ needs and continue to build out the Mozilla Developer Network to better engage with them.

Recap of the November 2009 Survey

As a refresher, here is a summary of the initial November 2009 survey. The main takeaways were as follows:

  • Our community is made up of a diverse set of developers that cover all aspects of web development from design to back-end work.
  • Open standards are by far the most popular technologies used for web development work.
  • Firefox is the most common browser used first by developers for testing their work, primarily because of the many developer tools and Add-ons available for Firefox and Mozilla’s strong support for web standards.
  • Firebug stood out as the most popular developer tool and many developers agreed that it is “absolutely essential for development.”

Results from the March 2010 Survey

Our second developer survey received 2,267 responses over two months from late March to early June.

For this survey there were several common questions from the previous one – about browser preferences – so that we could measure satisfaction over time and follow trends in browser adoption following the release of Firefox 3.6.
We also responded to the overwhelmingly enthusiastic praise of Firebug by asking for feedback on the most recent release. By obtaining more specific feedback on the latest version of Firebug, we hope to address any remaining issues to make it an even more effective and attractive tool for developers.

Developer Browser Preferences

We did not see much change in browser preferences from November 2009 to March 2010. Even considering a new iteration of Firefox and increasing competition from other browsers, the data still reflect general browser market share trends: the latest versions of Firefox and Chrome gained at the expense of older versions of IE.

The following data show the primary browsers developers use to test their websites:

Which browser(s) do you test your web sites against to make sure they are compatible?

November 2009

Tested Against
Firefox 3.5 82.03%
IE 8 74.63%
IE 7 68.23%
Chrome 60.23%

March 2010

Tested Against Percent
Firefox 3.6 80.17%
IE 8 70.23%
Chrome 62.37%
IE 7 56.18%

The numbers are unlikely to shift drastically because regardless of developers’ personal preferences, the top browsers listed above are the ones most commonly used by regular users, as demonstrated by browser market share data. Thus it makes sense that developers test against these browsers most often.

Firefox isn’t just the most popular browser for developing, according to the data below; it’s also popular for personal usage. It should be noted, however, that this survey was distributed primarily though Mozilla-related channels, so there might be some bias in the results; we address this problem later in the report.

Note also that the vast majority of developers were quick on the uptake switching from 3.5 to 3.6.

Have you tried Firefox 3.6?

Upgrading to Firefox 3.6

Although the vast majority of developers switched from 3.5 to 3.6, there were still some who did not. In fact, roughly 10% of the March survey respondents still used 3.5. The primary reasons for the continued usage on 3.5, however, had little to do with personal preference. Roughly half of those who still used 3.5 did not even know that 3.6 was released, while the other half responded that they didn’t have time to update.

One interesting note from the results was that a lot of developers still using Firefox 3.5 were on Linux distros that did not yet have the Firefox 3.6 package available at the time they took the survey. Given that 23% of respondents develop on the Linux platform, that could explain why so many had not made the jump.

What operating system do you mainly use for your development environment?

Unfortunately the data lacked specific details on why developers did not know about 3.6 or why they did not find time to update to the next version. With that said, regardless of the reasons, it is clear we should focus on facilitating the update process for future iterations of Firefox. We will start by promoting early betas and announcing new Firefox releases on the MDN website.

Feedback on Firebug 1.5

We all know that Firebug is important to developers, so we wanted to focus on getting Firebug-related feedback for this survey. Comments about Firebug echoed those from the November survey: the consensus is that “Firebug is the single most important tool in web development.” Indeed Firebug is considered such a critical tool in the developer’s arsenal that several of you asked us to package Firebug as a built-in component of Firefox instead of just as an Add-on; some users call the duo the “triple F”: Firefox and Firebug.

While the 1.5 release was a huge improvement from previous versions, developers weren’t shy about sharing their frustrations and feature requests. Many noted occasional stability issues, such as when Firebug is finding elements in document trees or taking certain Ajax requests. Additionally, we received several suggestions for improving the user interface, such as incorporating more Firefox-native design elements, increasing the size of the “Deactivate Firebug” button, and removing elements like the “Quick Info” and “CSS Overview” boxes.

One data point that stood out was that about 22% of developers had not tried Firebug 1.5 at time they took the survey. Considering that it was released in January and the survey was open from March to June, we would have expected that the adoption of such an important tool to be higher than what the data suggests. This presents an opportunity to better communicate new releases and raise awareness among developers to make sure they are up-to-date on the latest development happening with Firebug.

Have you tried Firebug 1.5?

For those of you who are interested in learning more about documentation, features, and related news, visit the Firebug website. Along with regular blog posts from the team, the site will host community forums for discussions with community and Firebug team members and offer ways to get involved if you want to contribute to the project. Firebug 1.6 development is well underway and we’ll continue to see it evolve to meet web developers’ needs.

Next Steps

Thus far your feedback via our first two surveys has been invaluable as we strive to build a better open Web through the Mozilla Developer Network. We now have a decent snapshot of the type of development you do, the technologies and tools you use, and the browsers you prefer for both work and personal use. The insights we have gained will help us refine the MDN roadmap and guide the programs we develop over of the next year to better engage with developers and build out the MDN website to meet your needs.

Our next step is to move beyond these initial data to get a larger snapshot of the developer community. We will start by designing an informal survey to get a grasp of what developers here at Mozilla and within our immediate community have to say about the tools and resources they find the most valuable for their work. We plan to follow that up with more research on the web developer community as a whole by distributing an industry-wide survey.

The goal for Q3 is to design a survey that can be distributed to a more diverse and unbiased global developer community. We plan to launch the new survey later this year and will look to you to help us reach the right mix of developers. Ultimately our goal is to have the clearest possible picture of the global web developer community and how it views the current “state of the Web”.

Since this is my first post as an intern for a tech company, I figure I should title it in classic programmer’s style.

My name’s Brian, and I’m a Developer Engagement Intern at Mozilla this summer. I will soon be a junior at Stanford. Generally, I’m pretty bad about updating blogs, but I’ll do what I can to keep the world updated on what I’m doing to keep web developers on Firefox. Looking forward to a great summer!