Jon Mountjoy's Blog

Google and others just launched Android. I'm more interested in how they bootstrapped their community though—it's obvious that they really thought this through and put a lot of effort into creating a viable platform on which a community can be built. This is in contrast to Apple and its iPhone Developer Center, which has no community support at all.

Android: Overview

• Type of Community - This is a developer community, and they have an audience of developers.
• Website - clean, clear, wonderfully free of annoying copyright, trademark and other company logos, a touch of graphics. Google is mentioned only once, discretely in the footer, and I think that's just because it's hosted on code.google.com. Emphasis is on what matters: Getting Started, the blog, the forums.
• Features - website, documentation, APIs, code samples, videos, downloads, blog, multiple forums (with email subscription and feed support), some identity, SSO
• Lures - a $10 million contest

iPhone: Overview

• Type of Community - This is a not a community site, it's a resource site for developers
• Website - clean, clear, a touch of graphics. Emphasis is on what they think matters: getting resources into developer hands, not on building community.
• Features - website, documentation, APIs, code samples, SSO, "connect to the experts" tech talk videos
• Lures - Listing in Apple web apps directory

Android: Purpose and Business Goals

The business goals are, I imagine, to support the adoption of Android among developers, and in so doing help the Open Handset Alliance Project succeed. The site has focus; it's purpose is clear. They obviously understand that developers want code, want HTML accessible API documentation, sample applications, SDK downloads and a developer forum.

iPhone: Purpose and Business Goals

The business goals are, I imagine, to encourage developers to write applications for the iPhone. There is already a huge audience out there scratching at the walls to do this sort of thing. The site is clearly a resource site. There is no hint of community here. I suspect they may be wanting to drive ADC registrations either - why else hide developer content links until you've logged in.

Android: Supporting the Audience

These guys have gone out of their way to support the audience: All the major operating systems are supported, with emulators, SDKs, code samples and IDEs. They're going out of their way to make sure there is no excuse. If someone is even remotely interested in this thing, they will be able to write their first application and deploy it to an emulator in 30 minutes. They've tried hard to remove any excuse for getting started and developing on their platform. They want you to succeed and have done a tremendous amount of work before the community was even launched to try and guarantee its success.

iPhone: Supporting the Audience

These guys have produced a rich set of resources that will allow developers to write web apps for the iPhone (SDK support is coming later). Since web applications are OS agnostic, they ostensibly support all platforms. In contrast to Android, they have not tried all that hard to remove any excuse for getting started. There's no clear downloads or suggestions of IDEs for example. They do have code samples, but little in the way of how to host them, how to integrate with other platforms etc.

Android: Content

The website has superb documentation. There's a "what is", getting started (including tutorials), developing applications, developer toolbox, reference information, sample code and FAQs. It's great to see the reference information online. Like most Java-based code bases, it's all available in HTML format. That means other developers can point to it in discussion. I see so many communities try and do this with PDFs, or worse, with documentation embedded in a download. That just doesn't work.

iPhone: Content

The website has great content and technical videos (delivered via iTunes). A full reference library documenting all the technologies and a set of sample code. The only other content is a set of iPhone Tech Talk Videos. I find the video delivery a little distracting actually. Because they're not embedded, I can't just "hit play" - it lacks immediacy and means I have material scattered over a website and my iTunes. Then again, I can play them on my future iPhone...

Android: Analysis

Here are a couple of things that may improve the community:

• Integrated Identity - they have some identity. For example, David McLaughlin, who I suspect is part of the community team, has his ID surfaced as David McLaughlin, Android Advocate. That "Android Advocate" is a nice touch. The unfortunate thing is that I cannot click on David's name and read his bio, find out what else he has written - which will lend to immediately increasing his identity, reputation and history. In fact, I can view his profile via his newsgroup postings, but they're lacking integrated identity.
• External Resources - while a community blog post does point to external communities publishing material on Android, they don't do a good job of surfacing this activity on the website. They could do with an article listing, perhaps community rated.
• Content experts, evangelists - while they undoubtedly have them, I don't know who they are, where they're speaking, what they're doing or what they're saying. It would be great if these folk are blogging. Of course, it's early days yet.

iPhone: Analysis

It's rather odd that Apple haven't engaged the community in any way. Perhaps that will change going forward, but there's no support for blogs, externally authored articles, or even the most fundamental in a developer community: the forum. In other words, they certainly don't have the infrastructure surfaced on this site on which to build a community. They also demand registration before giving developers access to the most basic of resources. A strategy by a company confident in what it's offering and that this hurdle won't discourage potential audience members, and a company that obviously wants developers to sign up for their developer program. All of this may be coming later. Perhaps they're waiting for the iPhone SDK to come out (next year). Some may ask if it's even necessary. There's already hoards of developers chomping at the bit, healthy discussion in external blogs, and perhaps there is a forum hidden on ADC's forums. Having said all that, it's hard to believe that a forum and community would not help Apple, or more importantly, these external developers. Sharing expertise, knowledge, tips, best practices—these will all help Apple in the end.

Android: Interesting Developments

Single Forum, Later Split: The community is a week old, and they've just split the single group (I think it was single last week) into 5 groups - beginners, developers, internals, challenge and discuss (water cooler). What's great is that they started with a single forum, and split it later as demand rose. So many new communities make the mistake of starting with a bunch of forums, all forlornly empty. Stats: The beginner mailing list now (Nov 17) has 102 messages, and the developer mailing list 3791 messages. It was at 2900 two days ago - that's a lot of growth. Last update: 17 November Update: Carlos Perez has a great take on the two communities. Technorati Tags: apple, iPhone, community, google, android