Google’s Android project is in serious trouble. They’re taking too long to iterate the SDK, and aren’t providing developers with enough information about its progress. At the same time, developers on the rival iPhone platform are enjoy stellar success.

Needless to say, Android developers are not happy, and are readier than ever to jump ship. Google’s not doing much to prevent this - the only Google voice in the discussion was that of Jean-Baptiste Queru, an engineer, who also remarked that he would “get into trouble for posting“.

As a further insult, developers recently discovered that an elite few have been secretly receiving updated versions of the Android SDK. This is not a good message to be sending the development community, particularly when an attractive characteristic of the platform is openness.

Android’s success or failure will largely be determined by the degree to which the platform is embraced by developers. So surely, Google would see Android developer relations as a key priority. But rather than embracing the community, Google has antagonised it.

So why is it so difficult for Google to be on top of developer relations? Why is there no obvious liaison - somebody who has the requisite technical knowledge, a ubiquitous presence, authority to answer developers’ questions, and a desire to expeditiously resolve conflicts? Why is there no individual whose sole responsibility is to complete the communication loop?

My intuitive response is that there’s a paradigmatic reluctance among the Android team to view third-party developers as partners and assets. Perhaps this is due to the pressure of working hard on a much anticipated product, resulting in myopia. Or perhaps it’s due to Google’s cultural of producing fantastic products in a self-reliant manner, engendering mistrust or undervaluation of third party developers.

Whatever the reason, there is no excuse. Amicable developer relations are vital for the project, and not should not be difficult to maintain.