Unboxing the Nexus One…

January 21, 2010

Did you unbox your phone like this?


If  so, then you can reduce your monthly fee by £15 by simply converting to the Simplicity 20 tariff on Pay As You Go.

At £20 per month for 600 mins + 1200 texts and with unlimited internet, free cloud/open zone wifi and visual voicemail – this is actually a better package than I had on my £35/month (18 month) iPhone contract.  Crucially, this is a one month rolling contract so you are not tied to 02 for another 12/18/24 months.

Also, don’t forget to unlock your iPhone from o2!

Since the start of Google Wave there has been a serious issue with the Wave api that has precluded some really cool applications: Issue 406: Robot cannot set a gadget’s state during gadget state update event.

This is a bug that prevents your really cool server side robotic wave participants (robots) from manipulating the state of gadgets (such as maps, forms or any kind of web UI) that are embedded within a wave.

Douglas Linder has provided a patch to to current Java api and a compiled jar file for convenience.  Check out the details here.

But even more exciting is that there is a new api planned for mid February which completely addresses this problem and many more. Details of this can be found on the January 6/7th office hours on the developer wave sandbox  (you will need a sandbox account to view this).

For me, the Nexus One had one huge feature missing yesterday – Multi-touch. It was completely glossed over during the press announcement and when asked about it during the Q&A, it was dodged by an uncomfortable looking Andy Rubin.

As, I watch the video back Peter Chou, the CEO of HTC, is very cool and understated in his delivery when he says “yeah, we thank that this is a great phone, one of the best”. When specifically asked about multi-touch, Peter says that it is available on the Droid Eris, implying that it could have been included in the Nexus One. When Andy Rubin was asked specifically if the Nexus One might one day support multi-touch, he answered “we’ll consider it”.

The key here though is that the hardware is *not* capable of multi-touch (also confirmed by UK Android developer advocate at Google, Reto Meier http://bit.ly/5EfWL9). So while I was disappointed that some other things such as an improvement in the market place were not delivered today, I know that these can be addressed in a future software release. However, I do not believe that this is possible for multi-touch on the Nexus One.

So, I conclude that this can only be a tactical business decision taken by Google. Of course this makes sense, when they release the next version of the Nexus One they’ll really need a way to (physically) differentiate it besides just adding a keyboard or incrementally improving the storage, CPU and memory specs. Apple play the same game e.g. releasing the new iPod touch in September without a camera. I just think that Google should have been better prepared for the question since it was such an obvious one.

Edit:  Clearly the Nexus One device itself does support multi-touch (as reported here http://techcrunch.com/2010/02/02/nexus-one-multi-touch/) since Google have recently provided an over the air update that enables pinch zoom on photos, google maps and the web browser.  So why the lack of multi-touch to begin with?  It looks as if there was a gentlemens agreement with Apple from the days as postulated here http://www.pcworld.com/article/159260/google_backs_off_multitouch_to_please_apple_report_claims.html (when Eric Schmidt was on the Apple board).  Now it seems all gloves are off.