Paul, Ryan.  "Developing Apps for Google Android: it's a mixed bag." Ars Technica.  December 19, 2007.

In this article from computer enthusiast Web site Ars Technica, correspondent Ryan Paul describes his first hand experience using Google's Android development kit.  Paul begins by describing the outcry of developers who are frustrated with the shortcomings of the development kit.  According to Paul, one of the most critical problems with the kit is the lack of a public issue-tracking system.  As it stands, Android users are able to report issues with applications and these reports are then added to Google's own private issue-tracking catalogue.  Paul notes how companies like Skype, Nokia and Trolltech have all successfully developed public issue-tracking systems, and thus one should expect Google to be able to do the same.  As it stands, Adroid users who report issues have no way of detecting trends in issues nor are they able to know when or if an issue will be fixed until after Google fixes it.

While the lack of public issue tracking presents a serious problem, Paul is also sure to praise the Android software for its strengths.  He notes how an Eclipse plug-in makes repairing bugs relatively hassle-free, and he praises an application in the development kti that allows developers to easily test how their applications will look onscreen.  As mentioned, Paul used the Android development kit to create his own application - a Twitter client.  In the end, he was able to do so in 130 lines of code - an impressively small amount, according to Paul.  Overall, Paul seems optimistic about the Android software.  He describes it as a "definitely viable and effective platform for application development" and he sees the problems with the software as stemming from Android's being in the early stages of development.  Nevertheless, many of the problems with the software are inexcusable and need to be addressed in order for Android to remain a contendor as a marketable mobile operating system.