The Catch-22 of Application Development on Windows Phone

Published by at

Without resources you cannot code anything, and the modern start-up has very few resources. So why would they write for Windows Phone, Nick Bilton asks at the New York Times. And he is right, deciding which mobile operating systems to support is a tough call, and one which does not have an easy answer. Windows Phone might have a lower installed base, but in some cases it's proving a better return than the reach of iOS.

In a nutshell, the problem is this:

Start-ups can’t devote resources to building apps for Windows Phone 7 until more customers buy phones that run on the platform. But, customers will not flock to Windows Phone 7 until their favorite apps exist.

There's a good bit of research and discussion on show here, but unlike some posts, this does go beyond stating the problem, but states teh problem and hints at a solution. Or at least Bilton allows Dave Morin (Path) to point out a way for Microsoft to short circuit the resource issues highlighted in the article:

Microsoft should continue meeting with developers, host MeetUps and publicly talk about how they are pushing the envelope in terms of what a user interface should be on a mobile phone. One of the things that Microsoft has is it is really flush with resources and capital. Comparatively, most start-ups are not.

Subtle it is not (and it's our emphasis) but he's right You need skin in the game, and if Microsoft want to stay in the biggest game on the planet (mobile), then there is a significant buy-in. Let's see how well they manage it - but I'd love to see them ensure Path makes it to Windows Phone. And Instagram. And a long list of other must-have apps...

Source / Credit: Nick Bilton (Bits, New York Times)