Lots of money's been spent trying to catch up to
RIM. Billions of dollars, I'd guess, if you added up the over quarter-billion of VC spent on
Seven,
Visto, and
Good, and the other attempts by Microsoft, Nokia and others. So why does RIM keep winning against such incredible odds?
My guess? RIM's got an end-to-end solution for
BlackBerry that looks a lot different from everyone else.
Motorola,
Nokia,
Microsoft... everyone else made the bet that mobile would evolve like the PC did: one company provides the hardware, one the operating system, one the email application, and whether it's an ethernet/WiFi/EDGE/EVDO/etc. network connection, it's all good ole' TCP/IP back to your mail server.
So, for me this generally looks like:
- WiFi
- Entourage
- Mac OS X
- MacBook Pro
But it's also been:
- WiFi
- Outlook
- Windows Vista
- Parallels
- Mac OS X
- MacBook Pro
... and you know what? It works pretty well. The folks making the OS, hardware, and email app didn't really need to know one another terribly well.. and they didn't need to know the mail server creator. The PC industry's evolved to the point where each of those components by itself is (generally)
good enough, so they can be
decoupled from one another and things generally work.
So if I look at a
Treo, it's basically running Palm OS or Windows Mobile, with Outlook/Visto/Good/Chatter running on top... and it doesn't really matter whether the network's CDMA or GSM. The same is true of the Nokia stack: just substitute
Symbian for Palm or Windows Mobile.
The difference? Palm's a horrible OS (crashes all the time, can't run more than one program at a time well, etc.) Windows Mobile is better, but not MUCH better (eats battery, it's clunky/hard to use/etc.), and Symbian's a usability nightmare: it was developed for smartphones, but seems more at home on a normal phone than an email device.
The Nokia E61 is (to me) a great example of the failure of Symbian, and the OS/Hardware/App split... Here's a phone with 3G/EDGE/WiFi, an awesome screen and lots of memory. On paper, it's
awesome. Ever try to use one, though?
Let's start with WiFi... Symbian is an OS that feels a lot like it was built by wireless engineers. You'd think that the phone could intelligently switch between the GSM and WiFi networks as appropriate? Nope. You've got to create "access points" and "access point groups" with combinations of GSM and WiFi networks in them, and hope that the application you want is able to understand what a "group" is... So, that snazzy and snappy WiFi radio? It's basically useless.
What happens when you get an email on the Nokia? Well... it's about 5 button presses to get to the email that made the device buzz... and that's if you can figure out
which inbox your message landed up in. Was it an SMS or an eMail? And why do files sent by Bluetooth end up in the same inbox as text messages? I don't mean to pick on Symbian or this particular phone... it's just an example of a bunch of different people building a bunch of different pieces of the overall solution, and having the end result be an ugly mess.
RIM took a far different path: they own the operating system, the email app that's on the phone itself, the servers that compress and push the messages to you... they even use their own messaging protocols, because at the time they built out the BlackBerry device and network, TCP/IP just wasn't good enough.
In
The Innovator's Dilemma, Clay Christensen makes the point that in the early stages of a market, the components for a complex product are - probably - by themselves not good enough, and the only way to create a
total product that's good enough, is to do it all yourself. As the market evolves, though, those individual pieces end up being good enough... and it's easier to just pull together "best of breed" pieces to build your solution.
So, where are we in the mobile cycle? Hardware's getting pretty good... the networks are pretty snappy (so TCP/IP is just fine, thank you)... Operating systems? Well, Symbian's still in need of a major redesign, and Windows Mobile is still pretty clunky. It's curious that the mobile operators and handset vendors seem to have realized this earlier than their PC counterparts did: things like the Linux/Java initiatives, and the Java standardization projects suggest that the OEM's and the operators realize that they've all actually got more to gain by creating a standard operating platform that
works and allowing developers to create and innovate, instead of spending time building more fragmented, broken platforms.
So until the OS problem gets really, deeply fixed, I don't see RIM having to really worry about the competitors taking over anytime soon. That said, everything else is really getting to the
good enough stage... and once the operating systems get there, we'll finally be where we are in the PC world: innovating and competing in the application space, not really the OS/infrastructure stuff. So what's RIM's play in
this world? I'm not sure... but I think some of the things that made them wildly successful over the last few years have changed. Maybe it's converged devices, consumer devices, and the like. (Mind you, we're probably 2-3 years away from this happening, so I'm sure they'll be fine :-)
NB: As I write this, my Berry's receiving weeks old messages from Gmail... I don't know whether it's Google's fault or RIM's... but for two companies that work pretty closely together... they ought to do better than this!