Commentary

Marin Perez
 

How Is Google's Android Shaping Up?

Ever since Google's Android was announced, we've been itching to see a handset running it. Can this first phone -- which will almost certainly be dubbed a GPhone by the press -- possibly live up to the hype?

Ever since Google's Android was announced, we've been itching to see a handset running it. Can this first phone -- which will almost certainly be dubbed a GPhone by the press -- possibly live up to the hype?We got a tantalizingly brief taste of HTC's Android-powered Dream device at Google's I/O developer's conference in May, and it was incredibly neat:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But since then, the rumor mills have been at full-tilt for the mobile operating system. First, the Journal says devices will be delayed due to holdups with China Mobile. Then, we hear whispers that Google's much-touted openness isn't so open. Throw in claims of an Android-Symbian merger, and even more reports of handset delays, and you can't help but get a little down on Android.

Through it all, Google maintains that the OS is on track, and a manager recently said the core operating system was about 80% complete. Recently, some blurry footage has leaked that supposedly shows an HTC handset running Android:

It's difficult to know if this is even real, or if it's the HTC Dream that everyone's been waiting to see. Let's hope it's not, because this handset just looks incredibly dull and boring. Sure, from the brief glimpse, the OS looked responsive and quick, but the Sidekick-like keyboard and flip-out screen look incredibly ugly.

It's still early, and I'm not going to judge a handset or OS by some YouTube footage that could be faked. But, I think some negative opinions on Android are already being shaped, and Google will need to have some "Wow" at the upcoming CTIA Wireless show to get potential customers and developers excited.

What are your thoughts on Google's Android so far?


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