I read over at ARS that Google is managing to piss off its own staff, as well as 3rd party developers by being tight lipped regarding Google Android progress.Anyone who's read Wikinomics will know that many companies like IBM have managed to harness the power of open-source technology to improve their businesses massively by:
a) reducing their R&D budgets
b) improving products at a much faster pace by opening up business problems to minds who aren't on the company payroll.
Open source encourages meritocratic hierarchies where useful, and regular contributors to the community are rewarded with respect (and quite often highly paid jobs within technology companies). But more importantly, it also encourages an agile eco-system of innovation, problem solving and fast moving product improvement (which sadly is often lacking in any corporate environment despite the number of 0's within their R&D budgets).
Google in some ways is seen as a big player in open-source technology due to the freely available API's which developers can download and then use to build tools for Google products, such as these useful Google Map mashups. These allow users to create value by overlaying different types of information over Google Maps to produce a new product with new functions like seeing easily what crime rates are like in local areas, or where new flats are coming onto the market for sale or rent.
So what are they doing to piss off developers and their own staff internally? They're going quiet is what. Open source communities are built on transparency - where some IP is kept secret for business sensitive purposes, but where much IP is made transparent to add value to the community, in the hope that the community will in turn create even more value from that IP than you are able to do so on your own.
Android developers are pissed that Google is prioritising getting a working handset above and beyond the release of an improved SDK (this allows developers to make stuff more easily for Android). But more over - Google aren't communicating with the very community that will in fact be making Google Android a valuable product. Without keeping your community of developers informed, you risk losing them to another mobile platform... like the newly made open source Symbian software which Nokia is looking to capitalise on.
Why is this bad you might ask? Well think of Android as a superstructure; building blocks that provide limited functionality, but at the same time make it very easy for other architects to slot their own rooms into.
Think of a big skyscraper with only big empty rooms in it... not very useful is it? Well the developers are the people who will make the easy access shopping malls, the fantastic hotel rooms and lush restaurants (maybe I'm taking the imagery too far?).
The developers are the makers of ideas and applications - these are the things which will ultimately make a mobile phone desirable. A handset with potential isn't desirable to consumers, a handset with a fantastic UI and a wealth of useful applications is.
So... Google - wake up and smell the coffee. Don't screw this up. Talk to your developers, and treat them as equals - you are in a horizontal relationship with these people who are making your mobile environment valuable - act as if you're grateful rather than pushing them away and remember the whole time that they're putting in hours of labour at no cost to make Android more useful, desirable and valuable.
-tobeconfirmed-






