Commentary

Serdar Yegulalp
 

Here's Hoping Google Can Fix The Phone UI Problem

Google's "vapor-phone" announcement (as some people have branded it) has me hoping they can do something about the mobile phone market that so far only Apple, of all people, has done anything about: Make the phones less of a clumsy eyesore.

Google's "vapor-phone" announcement (as some people have branded it) has me hoping they can do something about the mobile phone market that so far only Apple, of all people, has done anything about: Make the phones less of a clumsy eyesore.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I talked to a friend, a sometime Mac user, about what Google was cooking up, and his comment was: "I don't see how Google brainpower can fix the phone makers' demonstrated incompetence at making a complex gadget that people can actually use."

I knew exactly what he meant.  I recently replaced my Samsung (T-Mobile) handset with a more recent model.  The hardware design was unquestionably better -- the phone itself was lighter and had more features -- but the software, which is of course totally closed-ended and impossible to change, was a huge step down.  The menu system placed some of the most commonly-accessed functions in the system several levels down, and some features (like instant messaging) were so excruciatingly slow they might as well have not bothered.  Now I understand why I got those features "free": they're virtually worthless.

Whatever else you want to say about the iPhone, it's brought something to wireless communications that has been given almost total short shrift until now: real, honest-to-Jobs ease of use.  People are apparently more than willing to set the price and the locked-hands policy with AT&T aside to have a good user experience.

Google, however, doesn't seem to be talking much, if at all, about user experiences.  They've got two things in mind: to build a platform that lets them easily extend their ads and search services to the mobile world, and to create a set of relatively open standards for mobile devices.  The second is how they plan to accomplish the first, and I suspect their commitment to Linux here is only insofar as that Linux is free and open, too.  As my friend pointed out, if Linux vanished tomorrow, they'd probably turned to FreeBSD or something similar to fill the gap.  They, of all people, have good reason to be platform-neutral.  They use their system to monetize their search algorithms; they're not "UI people."

I know I'd love to see an actual Google phone, something with the straightforwardness and unpretentiousness of Google's own site.  Sadly, that doesn't look like what we're getting -- not courtesy of Google, anyway. I suspect Google will leave specific implementations -- including UI -- to the phone manufacturers, the very people who gave us such abominations of design as the Motorola RAZR's horrifically laggy menus.  (Another case of great hardware, horrible software.)  And the odds of the UI wizards at Apple picking up Google's toolkit and building a phone with it are microcosmically small.  Maybe Google just figured that for all their know-how this was, indeed, a job for Someone Else.


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