Imagine, that crowd of many skills, tastes and perspectives. Imagine they all want to improve the software, and have the capacity to do it. This is the potential of open source and open API. If there are issues with the software, the volunteer developers will find it. If there's a new feature that could be used, it can be developed by the people, for the people. This practice is known as Innovation in Assembly.
However, it isn't as simple as releasing an API (although that can happen). Rather, akin to harness collective intelligence, an API needs to be made attractive to the users. The more an API appeals, the more likely a skilled and insightful developer will utilise it. Several guidelines for Attractive APIs can include:
- The API is easy to access and easier still to use.
- The service is useful and the API can add to or use it in a new way
- The business trusts their customers, and learns from them.
- Documentation is clear, concise and possibly in different languages.
- Having a business plan in place to consider possibilities
On Mozilla's own site, they listed five main objectives:
- Non-profit - Firefox is and always was free, people could donate if they felt it a worthy cause. This also enabled users quick and easy access to the browser.
- Track record - It claims to have a long history of making decisions for individuals and the Web as a whole. By making decisions that aim to be a win for everybody, Mozilla has acquired many loyal customers.
- Empowering - In contrast, they display their trust in the community by enabling the ability to modify and contribute to the software.
- Community - A powerful display of a harnessed collective intelligence; the customers are the developers.
- Challenger spirit - When Firefox first came out, it directly challenged Microsoft's Internet Explorer as a browser. Skip a few years later, and it still remains a strong competitor in the market.
References:
Nalla Senthilnathan (2004), How to design good APIs and Why they Matter, retrieved 23 March 2012
Marieke Guy (2009), What Makes a Good API then?, retrieved 23 March 2012
Mozilla, Mozilla Firefox Homepage, viewed 24 March 2012
Mozilla, Firefox Brand Toolkit, retrieved 24 March 2012
Interesting angle on innovation in assembly. I would not have considered a web browser as an example, but as you have defined above, Firefox not only provided the API, but created a whole community of developers creating content that extend Firefox. The developer community that creates add-ons, through innovation, add value to Firefox, thus in turn improving Firefox itself.
ReplyDeleteIndeed. While there's a certain criteria, it seems that anything that allows a community to contribute could already be following the Web 2.0 patterns. Though I suppose that IS the point of Web 2.0: participation of users rather than passively observing!
DeleteFirefox is a great web-browser, I usually apply it when I am surfing on the Internet. I found it is faster that microsofte web-browser. However, I would like to know how can we tell them where should be improved? And if there are some fresh functions we create, how can we know whether it matches with original product or not?
ReplyDeleteAll the information you require is on the official Mozilla Firefox website. The Contact Us page enables users to find support for various common issues as well as provide feedback and suggestions for future versions. While The website provides Features and Add-on pages, which list functionalities produced, I would say use your best judgement for whether something matches the original product.
Delete