On September 14, John Gordon posted a piece on his blog where another blogger
compared Windows Mobile to the iPhone and found Windows Mobile lacking.
At the end of his post, Gordon asks these questions, which I thought
deserved a more-complete answer than I could leave in a comment on his
blog:
- Why has Windows
Mobile been such a dud?
- Was it because each device manufacturer
(for many years) had their own version and they, not Microsoft,
controlled the user experience?
- Was it a deep architectural
flaw?
- A business problem?
- Microsoft’s
incompetence?
- All of the above?
Let me
start by giving a high-level overview of what I think has happened up to
this point, and then try to answer those questions.
Many, many moons ago, Apple introduced the Newton PDA into the handheld
space and showed the world what could be done with a PDA. Unfortunately,
Apple chose a massive form factor for its devices and kept the platform
fairly locked-down. Palm was able to come in with an inferior but
smaller device and effectively drive Apple out of the market they’d
more or less created.
Around this same time, smart
phones were entering the scene, along with a variety of platforms on
which they could be based. There was Symbian, Java, Palm, and some
others I’m sure I am forgetting, all looking to be the next big
thing in the smartphone space.
Microsoft, sensing an
opportunity to stuff Windows into more hardware, introduced Windows CE,
and later Windows Mobile. Windows Mobile has continued to evolve and
improve.
Arguably, Apple is trying to redefine what
a smartphone should look like. Certainly, the iPhone doesn’t look
like any other smartphone on the market (or at least it didn’t at
the time of its introduction). That’s no surprise. Apple is all
about flashy, highly-graphical user interfaces and cutting-edge-LOOKING
hardware.
Just as the early Mac OS made DOS and Windows
look like pale imitations of what a GUI should be, the iPhone is
challenging what a smartphone should look like. Will all future smartphones look like
the iPhone? I doubt it, though I suspect to some degree most will
borrow some interface design concepts from Apple (which in turn borrowed them from other sources, as I understand it).
Why has Windows Mobile been such a
dud?
What I think this question is
really asking is “Why haven’t Windows Mobile phones caught the
public’s imagination the way the iPhone has?” But before
I answer that, I’m going to answer the question as stated.
I don’t think Windows Mobile has been a “dud” if
you consider what Microsoft was setting out to do when it created
Windows Mobile. In fact, if you look at it from that perspective,
they’ve been extremely successful. The flaw in that question
is to assume that Microsoft’s goal in the design of Windows Mobile
was to showcase its user-interface design talent. It wasn’t.
When Microsoft created Windows Mobile, its goal was to claim a part of the
market for embedded operating systems and deliver on those smaller
platforms an experience that was as close to the desktop Windows
experience as the hardware it was running on would permit.
That’s why, when we look at what’s typically bundled with Windows Mobile we
see things like Pocket Word, Pocket Excel, Pocket Outlook, and Pocket
Internet Explorer (or whatever Microsoft calls them now). They
wanted the Windows Mobile experience to resemble the Windows desktop
experience. Thus, Windows Mobile wouldn’t (in any default
configuration) ever display a very revolutionary user interface (unless
of course Microsoft changed the interface in Windows similarly).
Compare this to Apple and the iPhone. Apple may have been
trying to create a “platform” of sorts, but it was very
definitely creating a specific device. As such, their engineers
and artists knew screen resolution, processor availability, hardware
limitations, etc., from the outset. They weren’t trying to
create an OS X for the embedded space, but a phone that happened to use
OS X at its core. Evidence of this is the lack of typical
“Mac” applications like iWork, iLife, and so forth on the
iPhone. Freed of the constraints imposed by trying to re-create a
desktop OS experience in a confined space, they were able to create
something much different than OS X or Windows Mobile.
Saying that Windows Mobile is a “dud” compared to the iPhone
is like saying that a Ford F-150 is a dud compared to a Mercedes 750IL.
If you’re a construction worker who needs to haul tools and
work equipment around, the Mercedes might be more fun to drive but
isn’t well-suited to the task at hand. Similarly, if
you’re looking to haul a bunch business executives to a conference,
the F-150 might be bit less refined than you’re looking for.
That doesn’t mean the F-150 or the 750IL is a dud.
They’re just intended for different uses.
In the corporate space, the iPhone would be the real
dud. Compared to Windows Mobile, it doesn’t support the
opening of Microsoft Word, Excel, or PowerPoint documents. It
can’t be programmed using Visual Basic or Visual C++. It
can’t run corporate applications natively. There isn’t a
wealth of third-party software (at least not yet) available
to run on it. It’s not available from a variety of vendors,
allowing you to find a device that meets your price and feature
requirements. It doesn’t hook up to a number of different
carriers (at least not yet, without hacking). It is, in fact, the
antithesis of what most business users need – which is a subset of
Windows functionality in a mobile package. Thus, as a corporate
phone, the Apple iPhone is a “cute little toy” but not a
serious business device like a Blackberry, Palm Pilot, or iPaq.
What I think the question really means is “Why hasn’t
Microsoft captured the imagination of journalists and the public with
Windows Mobile the way Apple has with the iPhone?” and again the
answer comes back that it wasn’t Microsoft’s design goal at the
start. And as nice a guy as he may be (or not, I haven’t met
him), Bill Gates isn’t the snake oil salesman that Steve Jobs is.
He just isn’t able to pitch Microsoft technologies the way Jobs
can make Apple seem like a technological magic shop.
Is There a Deep Architectural Flaw in
Windows Mobile?
Neither Windows Mobile nor
the iPhone’s OS X is perfect. Read most consumer-written (as
opposed to media-written) iPhone articles and you’ll hear stories
about the iPhone locking up, failing to answer calls,
responding slowly to screen touches, etc. Similarly, you’ll get
stories about Windows Mobile doing many of the same things. Why?
I don’t know. I suspect it goes back to computer science
education in the world today. Back when I was in school, we were
being taught to try to design elegant, efficient code that used as few
resources as possible. Today, with wristwatches that have more
power than our desktops had back then, there’s less emphasis on
designing clean, efficient code and more emphasis on cranking out
software to meet arbitrary marketing deadlines. As a result, I
think Quality Assurance (QA) as suffered across the board.
So, to the extent that there are any “deep architectural
flaws” in Windows Mobile, I’d say there must also be equivalent
flaws in “OS X
Mobile” in the iPhone or such problems wouldn’t surface.
There is in fact some evidence to indicate the Multi-Touch technology in the
iPhone isn’t without problems, either.
Again, the
main difference as I see it is that Windows Mobile was, when it was
designed, not aimed at the same market segment as the iPhone.
Could Microsoft have delivered an OS for the smartphone arena that
delivers the “oohs and ahs” that the iPhone does? I
don’t know. Given the impressive demonstration they made with
the tabletop OS a while back, I suspect they could.
But I’m not so sure that anyone at Microsoft could apply the
appropriate level of “Steve Jobsian” marketing to it.
Is this a Business
Problem?
It’s a
business problem in that Microsoft still hasn’t managed to figure
out how to generate that media feeding frenzy that Steve Jobs does.
Until they can, Apple will tend to steal the spotlight, even when
they have an inferior product or one that’s overpriced. But
it’s not a business problem in that Microsoft has accomplished with
Windows Mobile what they set out to do, which was to drive Palm and the
like out of the handheld space. In this respect, they’ve done
well. The iPhone isn’t a competitor in the same space, so
it’s winning in its chosen space by default.
Is this an Example of Microsoft
Incompetence?
I
can’t speak for anyone else, but I see a lot less incompetence
coming out of Redmond than I do out of Cupertino. Microsoft shares
OS release plans with its business customers. Apple doesn’t.
Microsoft makes available a great deal of training online, for
free, to customers. Microsoft hosts online discussions when
security patches are released, inviting a dialog with its customers
about them. They do listen to their customers a lot, but it’s
all done so quietly and behind the scenes that the typical Windows user
has no idea of the resources available from Microsoft at no charge.
Microsoft even furthers the Windows “cause” by offering
free visual development tools along with the more-expensive ones, tools
that can be more easily and quickly picked up than those Apple offers
for OS X.
I see Apple releasing patch after patch that
break third-party applications, hardware drivers, and the like. I
see iTunes not working so well on Windows. I see
Microsoft, on the other hand, adding all sorts of undocumented code to
Windows to allow legacy applications to continue working after a patch,
transparently to the user. When I submit a crash report to Apple,
it vanishes into a black hole and I never see it again. When I
submit one in Windows Vista, it tends to come back to tell me about a
solution they’ve found for the problem or a diagnosis of the cause.
Sometimes those solutions are given to me days or weeks later, but
I get them. My crash reports don’t just disappear.
Microsoft openly seeks security bug reports from the hacker and
research communities and implements fixes fairly rapidly.
Apple seems to attack security researchers, deny that there are bugs, and take an inordinate amount of time to apply fixes to OS
X.
The more I look and listen, the more I see two
things happening. First, I see the media willing to pick up on and
report anything Apple calls “news” as revolutionary and
unique. Second, I see the Apple customer base increasingly becoming disenchanted with their
products, disappointed that Apple has left certain
“obvious” features out of them… such as releasing the
iPod Touch with less storage space than most other iPod models,
releasing the iPhone with obvious bugs in it, delaying the release of Mac OS X so it can meet an
arbitrary iPhone deadline, and the like.
To be sure,
Microsoft has a long way to go before it will ever APPEAR to be as
innovative and “exciting” as Apple does. However,
I’ve seen an increasing level of “competence” appearing in
Redmond in the last several years. Consider the XBox.
Microsoft began in a somewhat laughable position and achieved a significant share of the game console marketplace.
That’s hardly the mark of an incompetent outfit.
If Microsoft decides to compete in the iPhone space, I’m confident
that they’ll be successful because they’ll take one major source
of income under consideration that Apple traditionally doesn’t: the
business enterprise market. They won’t deliver a
single-carrier, single-network device that can’t be used easily on a
corporate LAN. And they’ll likely deliver a device running an
OS that has been in the mobile space a lot longer than Apple’s OS X.
Just as with the Zune and the XBox, Microsoft will start out in an
“underdog” position. But it will learn, and learn well,
from its customers. Apple, it seems, only learns from Steve
Jobs…