A little bit of this, a little bit of that. @TheRomit on Twitter, expanded.
Windows Phone app problem
Over the weekend, I had a twitter conversation with the Wordboxer developers, trying to get them to port their game to Windows Phone. It brought to light an important point about the Windows Phone (and for that matter, Blackberry) app problem: most cool games and apps are being built by small shops or single developers who just don’t have the time to build and maintain more than one or maybe two versions of their app/game. I really hope the Windows Phone (and Windows 8) teams realize this and create ways and means to reach these folks and help them out with the education needed to have them port their apps.
I know with the addition to C++ and support for cross-platform game engines on both Windows Phone and Windows 8, things are easier in terms of porting, but the point is most devs look at market share numbers and shy away from the platform. Of course, the market share going up and reaching some level of respectability (10% in the US?) may automatically help, but until then, Microsoft has a tough problem on their hands. They have to increase sales of devices, they have to attract the big brands and they have to make sure the indie devs also consider Windows Phone, if not at launch, at least soon after.
Small devs really don’t have time to develop and maintain code for more than one or two platforms. Even though Windows Phone dev tools are arguably better than anything else out there, and porting is easier with Windows Phone 8, it comes down to resources. Here is a great example of that.
My turn to throw some reality into the mix. It is easier to develop/port to Windows Phone because testing involves a finite number of resolutions and device types. Especially if they focus only on Windows Phone 8.