<!DOCTYPE html>
<!-- ========================================== kroc camen of camen design ============================================= -->
<title>writing · Has Microsoft Missed the Boat With Mobile?</title>
<link rel="stylesheet" type="text/css" href="/design/design.css" />
<meta name="viewport" content="width=device-width, maximum-scale=1.0, user-scalable=no" />
<link rel="alternate" type="application/rss+xml" href="/writing/rss" title="Just writing" />
<link rel="canonical" href="/writing/missed_the_boat" />
<!-- =================================================================================================================== -->
	<h1><a href="/" rel="index">
		Camen Design
		<li><a href="/">all</a></li>
		<li><a href="/projects">projects</a></li>
		<li><a href="http://forum.camendesign.com">forum</a></li>
		<li><a href="/quote/">quote</a></li>
		<li><a href="/writing/" rel="tag">writing</a></li>
		<li><a href="/blog/">blog</a></li>
		<li><a href="/photo/">photo</a></li>
		<li><a href="/code/">code</a></li>
		<li><a href="/art/">art</a></li>
		<li><a href="/link/">link</a></li>
		<li><a href="/poem/">poem</a></li>
		<li><a href="/audio/">audio</a></li>
		<li><a href="/web-dev/">web-dev</a></li>
		<li><a href="/annoyances/">annoyances</a></li>
		<li><a href="/eve/">eve</a></li>
		<li><a href="/code-is-art/">code-is-art</a></li>
		<li><a href="/inspiration/">inspiration</a></li>
		<li><a href="/windows/">windows</a></li>
		<li><a href="/gift/">gift</a></li>
		<li><a href="/gaming/">gaming</a></li>
		<li><a href="/mac/">mac</a></li>
		<li><a href="/osnews/">osnews</a></li>
		<li><a href="/c64/">c64</a></li>
		<li><a href="/linux/">linux</a></li>
	<a rel="previous" href="/writing/why_wifi">
		older article →
	</a><a rel="next" href="/writing/fiverfox">
		← newer article
<!-- =================================================================================================================== -->
	<!-- date published or updated -->
	<time pubdate datetime="2009-09-16T21:06:00+01:00">
		<sup>9:06<abbr>pm</abbr> • 2009</sup>
		<abbr title="September">Sep</abbr> 16
	<!-- categories -->
		<li><a href="/writing/missed_the_boat" rel="bookmark tag">writing</a></li>
		<li><a href="/osnews/missed_the_boat">osnews</a></li>
		<li><a href="/web-dev/missed_the_boat">web-dev</a></li>
	<!-- licence -->
		<abbr title="copyright">©</abbr>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<h1>Has Microsoft Missed the Boat With Mobile?</h1>
	This article was <a href="http://osnews.com/story/22178/Has_Microsoft_Missed_the_Boat_With_Mobile_" rel="external">originally published</a> on <a href="http://osnews.com" rel="external">osnews.com</a>
	<strong>Sometime ago</strong> <a href="/writing/ie8-standards">I conjectured</a> that Microsoft made certain
	changes to IE8 to force ’Web standards forward and drop backwards compatibility as default (a very un-Microsoft
	move) because of the need for the ’Web to break out of the blinkered IE6 / Desktop-Browser view of content
	otherwise Microsoft would find itself unable to compete in the mobile space. It’s been over a year since that
	article and in such a short period of time it has become ever clearer that Microsoft’s mobile offerings, and their
	overall mobile platform strategy are failing against the dominant iPhone, the newcomer Android, and a re-invigorated
	Palm with WebOS.
	Microsoft’s mobile platform has been fragmented by the
	<a href="http://osnews.com/story/22028/_Microsoft_To_Adopt_Dual-Platform_Strategy_with_Windows_Mobile_" rel="external">decision</a>
	to offer both Windows Mobile 6.5 and Windows Mobile 7 at the same time (when it’s released). Windows Mobile 6.5
	will support limited touch capabilities, but it won’t be until the <em>end of 2010</em> that Windows Mobile 7 will
	provide full touch capabilities to compete with the iPhone. To distance the product from its past Microsoft are even
	renaming it “Windows Phone”, a shallow effort to try bury a bad reputation for a bad UI model.
	The lack of unification and clarity extends even as far as Microsoft’s rebuilt efforts to compete in the
	<dfn title="Portable/Personal Media Player">PMP</dfn> space with the Zune HD. Whilst the Zune HD is a lovely, well
	built product, the lack of a single focus at Microsoft and a lack of tight integration and cooperation between
	departments has even clouded the Zune strategy.
	In an interview the Zune Marketing Manager Brien Seitz’s response was
	<a href="http://daringfireball.net/linked/2009/09/15/zune-translation" rel="external">as vague as it was
	non-committal</a>. In what way is keeping Zune app development close to the chest and hoping that <q>if there’s a
	way we can work with Windows Mobile or another group inside the company that’s building an app store and take
	advantage of that, that’s something we’ll look into</q> competing with the iPhone AppStore? Or even
	acknowledging it, for that matter. Hoping that the Windows Mobile team will get their act together so you can
	leverage their store for Zune is not exactly enthusing budding developers with the desire to develop for the Zune.
	The problem is that there simply isn’t any—brace yourself—synergy… happening at Microsoft. Each department
	is doing its own thing and not working together on a cohesive, integrated system. Why does the Zune require its own
	music player and not just leverage Windows Media Player? Why isn’t Windows Media Player being upgraded to support
	even basic features, like podcasting, that iTunes has had for years? Why is it that you have to use the Zune Player
	to get these features? Are Microsoft really expecting people to install the Zune Player and go buy a Zune just to
	get podcasting capabilities? Where on earth is the thinking in Microsoft coming from? Their strategies seem detached
	from reality.
	The web-browser in the Zune <a href="http://news.cnet.com/8301-13526_3-10354240-27.html" rel="external">is an
	afterthought</a>, a port of IE6 for Windows Mobile that puts you through a tortured experience. The codebase is
	incapable of competing with Safari on the iPhone that supports the latest CSS and HTML5 features and lead the way in
	giving users a browser on a mobile phone that they would actually want to use.
	I’m left imagining that Microsoft has a hundred separate departments all rushing to compete with Apple on their

<h2 id="got-here">How Microsoft Got Here</h2>
	The boat that I alluded to in the title of this article is Firefox and the modern ’Web standards movement.
	Microsoft’s complete lack of movement with IE6 saw them totally blind-sided by a competitor that sprang out of the
	corpse of the enemy that they thought they had fallen for good.
	Before 2004 Microsoft were in the very comfortable position of having 95-odd-percent market-share and no need to
	change anything with IE. Even if the concept of web-apps and the cloud took off, Microsoft were safe in the
	knowledge that those web-apps would be written only for IE, using such wonderful technologies like Active X.
	Firefox changed absolutely everything. Microsoft simply didn’t feel threatened by a grass-roots movement to adopt
	an open-source browser based on the failed Netscape that Microsoft vanquished five years earlier.
	And Firefox wasn’t a threat—really. IE still came as default on Windows, businesses would still be using IE and
	that wouldn’t change anytime. Firefox hasn’t damaged Microsoft, their own inaction has.
	The ability to sway the market has been pulled from underneath Microsoft. Web-developers are coming up with exciting
	new apps using web-technologies not available in IE. And the market is responding, they’re happy to switch browser
	if it gets them extra features and gives them access to the websites they want to use.
	We’ve seen a complete crumbling to dust of that notion that you <em>need</em> IE. Nobody <em>needs</em> IE, except
	for businesses stuck with badly-coded Intranets.
	And Microsoft have not been able to inject any compelling reason to use IE either. Both IE7 and 8 were lacklustre
	upgrades that caused more headaches then providing people with things they’d actually want.
	You just have to run Firefox 3.5, Safari 4, Chrome 3 or Opera 10 next to IE to realise that there simply is no
	comparison. IE is beat in every single aspect.
	HTML5 adoption is <a href="http://html5gallery.com" rel="external">progressing quite happily</a> even without
	official IE support. Microsoft can no longer dictate what features the ’Web will have and when. If Microsoft
	doesn’t provide it then someone else will and that wasn’t the case in the IE6 days.
	Y’see Microsoft’s lack of progress with IE has left them unable to adapt to new emerging markets and
	technologies. The iPhone completely reinvigorated the stagnant SmartPhone market where companies were practicing
	such bumbling incompetence with their software / handsets that Palm almost killed itself even without Apple to speak
	of. The competition that Apple injected into the market sharpened everybody’s minds, and the products accordingly.
	That is, except for Microsoft which simply has nothing to show for itself. Microsoft has no single platform
	strategy. Windows 7 only fixes the problems Vista introduced, it doesn’t bring anything truly new to the table
	other than a big sigh of relief from users worldwide. It’s still a hulking great disaster of a user-space (hello,
	registry, didn’t know you were still there) that can’t adapt quickly enough.

<h2 id="gone-on">Gone on Without You</h2>
	I strongly believe that Microsoft are three years behind everybody else when it comes to technology and the ability
	to compete. Microsoft cannot just throw more money and programmers at the problem. This is an organisational /
	managerial problem that requires them to get the talent they already have working together toward a single platform
	strategy that can rapidly adapt and apply to new devices and markets.
	Trying to catch up simply isn’t good enough. Telling your clients that proper touch-controls won’t be coming to
	Windows <del>Mobile</del> Phone until the <em>end of 2010</em> is no good. Why not just use Android or WebOS
	<em>now</em>. Or buy a freakin’ iPhone.
	Nothing short of
	<a href="http://blog.chromium.org/2009/09/introducing-google-chrome-frame.html" rel="external">replacing the
	rendering engine of IE with Webkit</a> is going to stop the massive haemorrhaging of market-share that IE is
	experiencing. IE is passé now and once you’re out of the loop it’s going to take more than the odd feature and
	improvement to bring users back. The exodus is well underway and the IE brand has fallen foul of consumers.
	To win me back IE would have to be faster than Chrome, have the extensibility of Firefox and support bleeding edge
	CSS3 and HTML5 features like Webkit. Oh, and not suck UI and security wise. Does anybody seriously believe that
	that’s going to happen?
	By sitting around idly with IE6, Microsoft have let the ’Web overtake them. Innovation is happening faster than
	Microsoft can keep up. Microsoft are trying to catch up with competitors and social movements that are traveling
	<em>faster</em> than they are.
	I’m not saying that Microsoft are going to collapse and die and all that rubbish, instead I can see from the past
	that the future is going to be a place where Microsoft are no longer the ones leading the way. Their desktop
	market-share won’t drastically change, but innovation will move to the ’Web. A place larger, more diverse and
	faster than Microsoft and a place where Apple have positioned themselves riding right on top of the crest.
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
	<nav><a href="http://forum.camendesign.com">‹ Discuss this in the Forum ›</a></nav>
	<a href="mailto:kroc@camendesign.com">kroc@camendesign.com</a>
		<a href="/writing/missed_the_boat.rem">Rem</a> •
		<a href="/writing/missed_the_boat.html">HTML</a> •
		<a href="/design/">CSS</a> •
		<a href="/.system/">PHP</a> •
		<a href="/.htaccess">.htaccess</a>
	<form method="get" action="https://duckduckgo.com">
		<input type="hidden" name="sites" value="camendesign.com" />
		<input type="search" name="q" placeholder="search…" />
		<input type="submit" value="Go" />
<!-- =================================================================================================== code is art === -->