The Wall Street Journal on the Android SDK

I'm quoted in today's WSJ on some of the problems with the Android SDK.

Google Inc. claims its Android mobile-phone software will usher in a new era of wireless communications. But for developers like Adam MacBeth, Android has so far brought nothing but headaches and frustration.

Mr. MacBeth said he spent weeks trying to write programs for Google's much hyped mobile-phone software, but the Seattle-based engineer and entrepreneur found the developers' tool kit full of bugs.

"Functionality is not there, is poorly documented or just doesn't work. It's clearly not ready for prime time," said Mr. MacBeth, who earlier this year helped found mobile software start-up MergeLab.

I previously wrote about my impressions of Android, and in general I think the platform is a step in the right direction. I'm optimistic that future releases will correct many of these issues, but right now the SDK isn't really usable for anything beyond the most basic of apps. Many of the really interesting innovative features are the ones that don't work, such as APIs for XMPP, SMS, and phone.

I think Google's motivation to release this SDK before it was finished may not have been the best - beating Apple to the punch by putting out the Android SDK before the iPhone SDK, which is supposed to launch in February 2008. I don't think this will negatively affect the long-term viability of the platform, but initial adoption may be slowed until Google releases a "serious" version.