Jon Mulholland -

The case for and against buying a Nexus One...

As I predicted this afternoon, despite earlier reservations, I'm getting caught up in the hype surrounding the imminent launch of Google's Nexus One.

Driving home early to avoid the snow, I thought through the pro's and con's of whether or not to splash out on Google's new Android handset.  This is the case for and against as I see it:

For

  • I've been a heavy Gmail user for years and am unlikely to switch to any other email service any time soon (MobileMe doesn't even compare).  Android's mobile Gmail is excellent, certainly a lot better than using IMAP/Gmail on the iPhone mail client.
  • I also use Google Calendar to sync my 37Signals Backpack Calendar wirelessly, again I can't see me stopping using Gcal anytime soon.
  • Android's pull down notification system is brilliant and really useful.
  • Google Maps on Android is much better than Google Maps on iPhone.
  • I'm really impressed with the UI tweaks Google have made to Android 2.1; particularly the changes to the home and application screens and the new widgets included.
  • I'll be able to use Google Voice.
  • Being able to run background tasks will be pretty cool.
  • Two of the biggest services I'd miss if I moved from away from the iPhone (Dropbox and Gowalla) are both currently working on Android applications.
Against
  • So far my experience of the Android phone app (HTC Hero, Android G1) has not been good.
  • The next iPhone update (due June 2010) is likely to be a significant revision given that the the 3GS was only an incremental upgrade - should I wait and see?
  • I'm a heavy iTunes user - particularly podcasts for the gym - I'm not sure what Nexus One / (Mac) iTunes compatibility will be like (although maybe I could use DoubleTwist?).
  • iPhone Safari is still the best mobile web browser, the Nexus One apparently doesn't have multi touch so it's unlikely to be better.
  • I would really miss Tweetie if I moved away from the iPhone, it's my main social network lifeline.
What's a mobile geek to do..?

Loading mentions Retweet
Filed under  //   android   google   nexusone  

Comments [6]

The Google phone is very exciting, probably not going to tempt me away from the iPhone though

Like most mobile geeks, I'm really enjoying all the Google Nexus One news; it's starting to sound like a very nice device, and it's obviously a very interesting move by Google. Seeing their vision of what a modern mobile device should be, and how far Google feel they can push their services into our pockets will be fascinating to see.

I've already pretty much decided that I'm going to give the Nexus One / HTC Passion or whatever it ends up being called a miss though. Not because I'm a total Apple fanboy, or because I'm one of those crazies worried about giving Google too much access to my data - I'm a very heavy user of all of Google's services, and have been ever since I opened my first Gmail account back in 2005.

Why the reluctance then? Android has many positives - mobile Gmail is great, Google Maps on Android is better than on iPhone, multitasking rocks and Android's notification system is just plain brilliant. But at the end of the day - from my experience (G1, HTC Magic and HTC Hero) - Android is actually a pretty sucky phone.

I think Ewan hit the nail on the head yesterday:

My biggest concern with Google is their apparent inability to bring anything to market that is actually ready for consumers to use.  I’m talking, of course, about the perennial ‘beta’ labels that populate their technology.  This beta policy makes a ton of sense — and I think the majority of geeks like me are thoroughly delighted to see the company make frequent updates to their services.  I wonder, then, how they’re reacting to delivering a physical product that can’t be changed.

To say that the Android phone experience is a bit unpolished (even when tarted up by HTC) would be a massive complement; take the iPhone away from your ear to "press option 3 to speak to an advisor" and the screen lights up ready for use - easy! Try the same trick with an HTC Hero and the screen will have locked. Go to press the phones usual screen unlock key and you'll have killed the call. It's this kind of thoughtfulness that I think Android phones will always lack, mainly because Android devs don't have a maniacal Steve Jobs standing over them yelling - "not good enough, do it again."

The iPhone might have limitations, and the App approval process does appear to make some rather perverse decisions, but Apple's rigid control of the platform undoubtedly makes it slicker. We had to wait far too long for 'copy and paste' to appear, but when it did it was perfect. Does any other device honestly have this feature implemented as well as the iPhone?

I'm also rather dubious about one of the Nexus One's really big selling points - availability as a carrier unlocked device. If this is true I really applaud the move, it could be a watershed moment for the telco industry, but I'm just not sure Google will be able to pull this off. They don't have consumer goods distribution experience; I suppose they could rely on HTC's sales channels, but this would be a really big ask. Google has previously given away unlocked Android devices to developers only, could they be dong the same with the Nexus One, planning to release the device to the public via one of the carriers (my money would be on T-Mobile)?

Then there is my final nagging doubt; good as the Nexus One may be, in my mind it's really a second generation future mobile device (1st gen = iPhone, 2nd gen = iPhone 3G/3GS). I'm sure it will stack up well against the iPhone 3GS, Palm Pre etc, but really we're still watching Android play catch up.

I still predict that the really big mobile news of 2010 will be the major update Apple announces to the iPhone platform in June, so for the meantime I'm sticking with Apple.

This post is also published on Mobile Industry Review.

Loading mentions Retweet
Filed under  //   android   google   mobilephone  

Comments [1]

What Google has planned for Jaiku?

Google’s acquisition of Jaiku back in October seems a long time ago now – such is the pace of the technology industry I guess. Subsequent OpenSocial and Android announcements have stolen much of the limelight since, but I keep coming back to the Jaiku purchase. I have a feeling that Jaiku is a bigger piece of Google’s new jigsaw than we’ve so far realised.

If Google simply needed a micro-blogging capability, why go for Jaiku and not Twitter? Twitter after all is the market leader in this growing sector, with an established and enthusiastic user base. Jaiku is certainly popular (especially in Europe) – but not close to Twitter when it comes down to size, popularity and ‘zeitgeist’.

There have been quite a few comments to the effect that Jaiku provided Google with a cheaper alternative to Twitter. Whilst what Google paid for Jaiku is certainly less than they would have paid for Twitter, I’m not convinced this is the reason.

We know Google have money to spend. If the purchase of a pure micro-blogging service was strategically important to Google then I’m pretty sure they would have found the money needed to buy the current leading service. Anyway it probably would have been cheaper still for Google to engineer some kind of status messaging feature directly into Google Talk and/or Gmail if that’s all they were after.

Why Jaiku then? I think the answer lies in mobility, specifically location and mobile integration.

Let’s look at location first. Jaiku is I think unique in combining micro-blogging AND user location awareness. For the uninitiated, when posting status updates Jaiku has the ability to capture and share the location information (neighbourhood, city, country) of the poster in real time. So in addition to a message post Jaiku can provide real time location awareness of users. Hmmm that’s interesting…

And how does Jaiku do this? An integral part of the service is a client application for Symbian S60 platform mobile phones. The client uses location APIs within S60 devices to triangulate the handset (and the users) location based on nearby cellular network towers. The Jaiku client was in fact originally conceived as a ’status aware address book’, and as such integrates into compatible S60 phones to the extent that it also shares the phones (and again the users) status availability ( – General, In Meeting, Outdoor etc).

So in addition to a message post AND location awareness you also have deep mobile integration sufficient to identify the status of a user as well. That makes things really interesting, and its this combination that I think is the clever part. Consider this thought:

Post + Location + Status = Value

If you’re a user of Jaiku, or Twitter for that matter, look back through some of your posts and you’ll see that you’ve built an outline profile of your life. Reading through my Twitter and Jaiku pages it’s reasonable easy to deduce that I’m a Mac geek, a fan of American TV dramas, enjoy listening to Radiohead, suffer from occasional migraines, like Indian food etc etc. Now consider what value is added by a service that knows where you are and also whether it’s appropriate to contact you (through your mobile phone) as you post updates.

Jaiku potentially gives Google the Holy Grail – time relevant, location based targeting of information, personalised to a very high degree. Google + Jaiku is not a million miles away from being able to push appropriate advertising to individuals based on their profile, their location and their availability. Imagine walking down the high street and having your mobile phone pop up with a Google notification telling you that Heroes DVD box sets were 20% off at HMV today, or that a new Indian restaurant had just opened in that part of town. Some may find that scary, and reminiscent of scenes from the film Minority Report, obviously as a technology ‘enthusiast’ I’m thrilled at the possibilities it opens up.

It seems obvious that Jaiku is destined to become an integral part of the the Android platform over the next year. No doubt Google will want the Jaiku engineering teams expertise in building the features outlined above into the Android offering. This is why I think Google went for Jaiku, and this is why I think Jaiku has a big role to play in the next phase of Google’s advertising platform.

If this isn’t what Google has planned for Jaiku, they should certainly think about it.

Loading mentions Retweet
Filed under  //   google   Jaiku   microblogging  

Comments [0]

Personal Computing will be mobile – what Microsoft did to the PC, Google plans for the Smart Phone

The internet is predictably buzzing tonight with news of Google’s Android mobile phone platform.Loads of good commentary about, most of it already shared via Robert Scoble in his infamous link blog. I particularly liked Michael Gartenburg’s take on the announcement (’this will prove to be far more disruptive to the mobile industry than if Google had simply announced a handset’). 

I think I agree, although the really smart part is that the Android strategy strategy capitalises on where the mobile phone industry is heading anyway.  In doing so, Google kind of repeat Microsoft’s move back when the Personal Computer market was about to explode all those years ago.

Sure the mobile phone market is already huge, and in some mature markets handset sales growth has slowed recently.  But something interesting is happening at the moment.  The distinction between non-smart and smart phones is disappearing rapidly.  A second phase in the market is emerging as the ubiquitous ‘dumb phone’ takes on smart phone features and evolves.  The mobile phone is becoming the new personal computing platform – the GPS, HSDPA, Email, High Res camera functionality of today’s Nokia N95 and other high end phones will be commonplace in a year’s time.  As these feature sets evolve typical usage of devices is gradually ‘deepening’.  Two years ago mobile internet was for geeks only, now it is reaching the tipping point into mass adoption.

The mobile phone will more and more be the device we use to store our data and interact with pretty much everything we value.  Google has realised this, and is therefore rightly not looking to just capture the geek and enthusiast market as it could have done by launching an uber-connected device of it’s own manufacture today.  Google is aiming for everyday users like my wife, who want a cool looking device that is friendly to use.  Giving the everyday majority of users simple and useful mobile access to Google services is the aim here. It’s far better to let Samsung, Motorola, LG etc to do what they do best (continue to evolve the feature set of devices with mass consumer appeal), whilst Google captures the operating system ecosystem for this new era in personal computing.  Google is almost pulling the same trick as Microsoft did all those years ago – very smart!

Microsoft used to aim for a PC running Windows on every desktop. Google is anticipating a smart phone in every pocket and is aiming to be loaded on to as many devices as possible.  Personal computing will be mobile, and Google wants a big a slice of this.

Loading mentions Retweet
Filed under  //   android   futureofmobile   google  

Comments [0]