Lessons learned from the development and marketing of Mozilla Firefox 1.0

Abstract

This case uses first-person sources to put the reader inside the teams that developed and marketed the Firefox browser. A brief overview of the Open Source Software (OSS) development process and the various roles played by members of a software development community, as well as a brief summary of the browser wars of the 1990s that saw Netscape Navigator fall from the dominant browser in the market to a distant second place behind Microsoft's Internet Explorer, help provide context for the case. In order to adapt the OSS development model to support a consumer-oriented product, Firefox developers adopted four rules: ‘We want it to be small,’ ‘Let's not keep too many cooks,’ ‘All patches are not created equal,’ and ‘All users are not created equal.’ The development team established a goal of 10 million downloads in the first 100 days and a 10% market share in the first year as measures of success for the new browser. In order to compete with Microsoft in the browser market, the Firefox team needed to leverage the development community to reach millions of potential end users. By providing a web-based structure for collaboration, and through a series of top-down initiatives (providing marketing tools to the community), and bottom-up initiatives (receiving and disseminating marketing ideas from the community at large), the team was able to achieve its marketing goals. In so doing, the SpreadFirefox initiative created a marketing community with roles analogous to a software development community.