ro

A huge part of the mobile experience is still extremely subpar. No one has created a seamless handsfree experience. I briefly blogged about this 2.5 years ago, and I still feel like there is tons of room for improvement. I don’t blame the headset companies, as my Plantronics (and for many others Jawbone) headset works great… as a headset for phone calls. But using it is not easy. Voice dialing (calling a contact using voice recognition) is a very basic start. The iPhone has Voice Control, which is little more than voice dialing plus basic iPod controls. Android has the best solution right now, Voice Actions, which seems very promising. Yet it doesn’t work consistently with a bluetooth headset, and the commands themselves are too robotic for most users. There are also some solid apps in the space. Nuance’s Dragon voice to text is great. Siri (which Apple purchased 1.5 years ago) has a good amount of NLP (also uses Nuance) and allows for a variety of different commands. Vlingo, Google, and countless others have apps too. But it isn’t effective unless it’s integrated at the OS level and works with handsfree devices.

The obvious use case (especially in CA and other states where there are specific laws) is controlling the phone while driving. Some cars have tried solving this, but none (that I’ve tried) have done it well. But handsfree use cases can be more common- anywhere from multitasking to video chat would be improved by some sort of integrated headset. Wired headsets are obviously not easy to use (I feel like I’m always untangling mine). And wired headsets only work on a single device- bluetooth would allow for switching between iPhone/iPad/etc. where appropriate. Apple previously tried making a bluetooth headset (see here) but apparently gave up, I’m guessing due to technical limitations and lack of polish. The bluetooth spec has improved significantly, allowing for better quality and lower power consumption. A typical headset now can go days/weeks before a charge with decent use. My ultimate wish is that the headset would be able to charge directly from the phone via a mini charging connection or induction-based charger.

But the software integration is the most important – the headset and phone need to understand a variety of commands and output results using display and more importantly voice. Something like “look up directions to Mitchell’s Ice Cream” should return a map and read out the list of turns.  ”Schedule phone call with Mom for tomorrow at 3 pm” should read back, create a calendar item, and send an invite. The harder but equally important one command is “reserve a table for tomorrow at 7 pm at Aziza for 4 people,” which should use the OpenTable app, and read back available reservation openings and confirm. And the software should somehow know how to differentiate and use the appropriate device, whether an iPhone on the road, or the Apple TV at home.

My prediction (dream?) is this will be solved in the next major iOS (5.x) release, and that Apple will release a headset at the same time.

Google officially announced the Nexus One today, and it seems pretty cool.  I haven’t had a chance to play with one yet, but by most accounts, it’s worth checking out.  I believe it will be a successful device, along with the Motorola Droid and the HTC Droid Eris.  However, there seems to be a lot of sentiment that this is playing out like the PC vs Mac wars a decade or so ago, and that slowly app developers (and in-turn users) will all gravitate towards the more open Android platform.  The argument is that Microsoft excelled because it was hardware agnostic and did not control the ecosystem (thus allowing it to innovate), whereas Macs struggled because they controlled the entire experience (here’s a good take on this).  In the mobile marketplace, the argument continues, Android will eventually win out because it’s completely open.  Never mind the over simplicity (i.e. Jobs left, the hardware started to suck, etc.), there are some good parallels to make the analogy fit.

I, however, completely disagree.  This market is much, much more nuanced.  The reason is that there are two major differences between different phones that affect user behavior – input mechanism and screen size.  For example, here’s a list of the different screen resolutions for Android devices:

800 x 480
600 x 800
320 x 480
240 x 320
854 x 480
240 x 400
1024 x 600

And Android is only now becoming popular.  Some Android devices have keyboards, some are touch only, some have pointers, some have extra buttons, and some have sensors others don’t.  With the computer, everyone had a similar keyboard and mouse.  Users had different size monitors, but the big difference was that you could get away with cropping and not using the entire monitor for computer apps.  On a phone, where the screen is already so small, not using the entire space is much more significant.

This is the same issue that plagues Blackberry right now (well, that and terrible API implementation/documentation).  Whether it’s the Curve, Bold, Pearl, and so on, every device has a different resolution, and so apps need to be tailored appropriately.  I’m not the first to realize this is an issue (official Android documentation and another post).  The iPhone, on the other hand, has one screen resolution 320 x 480, and one input mechanism, touchscreen.

That all said, I believe that Android will thrive, but it won’t be the same way as Mac vs PC.  Bill Gurley’s piece (a must-read, in my opinion) begins to get at the nuanced differences, but Android is still a smartphone platform, which puts it head-to-head with the iPhone.   It is very lucrative for manufacturers and carriers to use Android instead of paying a licensing fee (they actually receive ad revenue share for using Android).  But for consumers and users of apps on both devices?  I still think the iPhone will be a better experience.

Two additional interesting factors to consider – if feature phones (i.e. non-smartphones) begin to adopt Android in full-scale, and the continued success of the iPod Touch and iTunes store (remember, you can’t use your iTunes music on a non-Apple device).

Apple announced today that over 2 billion apps had been downloaded – quite an amazing feat in little over one year.  Since I started using an iPhone, I realize that my favorite part is the App Store.  The touch screen and slim profile are nice, but it’s really the store that makes me love the device.  Perhaps I’m unique.  As a kid, I used to love getting the Sunday newspaper, especially on a snowy day, when the newspaper was cold and crisp.  After perusing the sports section and the comics, I loved leafing through the CompUSA and Circuit City flyers, especially the clearance and sales sections.  I could never buy enough cheap peripherals or hard drives.

The app store has taken over my previous excitement that I felt about the flyers.  Now I download Waze or buy Snapture rather than a trackball mouse or screen cleanser.  Instead of waiting for Sunday, I can just load up the store on a whim and see if there are any cool apps.  I wish there was more turnover in top apps, but the fact is that it’s far and away better than Blackberry’s App World (and I hear also Android’s and Palm’s, though I have limited first-hand experience).  It has the instant gratification element.  I wish that the iPhone allowed developers more flexibility, but as long as people keep releasing great apps, I will be interested.  And that’s the key – the moment another platform’s app store gets more traction, and their apps become more innovative than the iPhone’s apps in terms of quality and quantity, I will most likely switch over.

UPDATE: As I was loading up my blog to post this, I saw a very relevant argument that Blackberry needs to step up their efforts in the app store.  Worth a read…