Short Nerd Chief

What Should Google Mobile Do Next? Fix the Broken Stuff.

Posted by Fred on December 20, 2007

Judi Sohn at Web Worker Daily wants to know What Should Google Mobile Do Next?

As Google expands their supported platforms and applications in the mobile space, what do you want them to tackle next? Sync for Windows Mobile calendar? Gmail contact syncing? Stand-alone Reader or Docs? More iPhone-friendly browser applications?

To paraphrase the comment I left over there - should Google introduce new mobile products? God no. They should fix the ones they already have, most of which are broken in some way (other than the ones for the JesusPhone):

  • Gmail introduced IMAP support, which in theory should allow you to keep the messaging application on your phone and the web application in sync.  Unfortunately, on Windows Mobile it’s horribly, horribly broken.  HTML messages just show up as message headers with empty message bodies. Google knows it’s broken, they’ve known for over a month, and they haven’t said anything other than “Windows Mobile is not supported.”
  • An alternative would be the Gmail java application, which does a lot of neat things like prefetching messages for speedy access.  Unfortunately, on AT&T the application is unusable, thanks to the crippled java implementation AT&T uses to promote its own service offerings.  This isn’t Google’s fault, but they could easily fix it by either (a) releasing a signed java application, which would get around the security restriction (what Nokia ended up doing to get Widsets to work on the e62) or (b) releasing a native Windows Mobile application (like they did with Maps).  At the very least, Google should acknowledge the issue and explain what the problem is.
  • The new beta of the Maps application has a cool feature called My Location, which uses cell tower location to provide a rough GPS-like functionality for non-GPS phones.  Great if it works, but many handsets just say “location temporarily unavailable.”  The Blackjack and the Q are two primary examples.  Each of these devices does report location to the OS, which some applications are able to use (i.e. PhoneAlarm).  Google apparently doesn’t like the data the phone provides.  Again, this is not entirely Google’s fault, but they could fix it, if they wanted to.
  • The last time I used it, the Google Reader mobile site crashed Pocket IE any time you tried to mark all items as read.  The Q9h comes with Opera Mobile, which seems to work OK.  Opera Mini also works OK, although it suffers from the same problem Gmail does and is unusable on AT&T phones.  Google Reader also doesn’t play nice with Opera Mini - keyboard shortcuts don’t work.

It bears repeating that these problems are not necessarily Google’s fault.  Other mail applications can deal with Gmail’s non-standard IMAP implementation, for example.  But the mobile world is what it is, and if Google is going to play in the mobile space, they should figure out a way to make their applications work properly.

One Response to “What Should Google Mobile Do Next? Fix the Broken Stuff.”

  1. portaleco Says:

    Both major players Google and Microsoft have to learn the lesson that they should stick to standards or work with the web community to create new ones. Microsoft is notorious about “promoting” IE with all kinds of bugs (they call it advanced features) their proprietary stuff e.g. Sharepoint administration works only with Internet explorer. Google seems to go the same road with all kinds of client AJAX, wich is not available on mobile devices. I hope both will learn their lessons. I am using Opera Mobile 4.0 on a solid Konia Java platform with my mobile phone - it works even in harsh environment. However, they can’t do miracles, when MS and Google use proprietary functions on the client. I really don’t want to be locked in by any player!

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>