Commentary

Developers: Android Doesn't Work

Looks like Google doesn't have the Midas touch after all. According to reports, a sizable number of developers who've been working with the SDK for Google's Linux-based Android platform say it is full of bugs and often doesn't work at all.

Looks like Google doesn't have the Midas touch after all. According to reports, a sizable number of developers who've been working with the SDK for Google's Linux-based Android platform say it is full of bugs and often doesn't work at all.It is not atypical for there to be bugs in new software. The Wall Street Journal is reporting that a large number of Android developers are encountering serious coding errors in the SDK. It cites the experiences of one developer, Adam MacBeth, who has been unable to get an application working in Android after working on it for weeks.

Said MacBeth: "Functionality is not there, is poorly documented or just doesn't work. It's clearly not ready for prime time."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Ouch.

This is an early stumble for Google. Google needs the developers to be happy with the SDK if it expects the platform to gain any legs in the market. If they can't get applications to work because the coding is all messed up, Android might be a very short-lived experiment or fail to have the impact Google hopes for. The developers who WSJ spoke with also said Google has not be very responsive to their complaints.

The news isn't all bad, though. The WSJ wraps its article with thoughts from professional software engineer Rick Genter. Mr. Genter said, "While Google's mobile software is buggy, it isn't necessarily any worse than any other software at such an early stage."

Let's hope that's the real story here.

Since Google doesn't plan to make the platform available until the second half of next year, it and the developer community have ample time to get the bugs worked out.

What about you? Any other developers out there experiencing trouble with the Android SDK?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links