Come on man, it's not like the mobile division has the power to unilaterally chart the course for Microsoft's mobile strategy; with MS, every division is subser

Come on man, it's not like the mobile division has the power to unilaterally chart the course for Microsoft's mobile strategy; with MS, every division is subservient to the rest and they're co-shackled, usually in support of Microsoft's core money makers (Windows and Office.) The mobile division is not just coding for the present and the future, but also the past. If they manage to get half the developer attention that the iPhone gets, I am certain MS will demolish both iPhone and Android because they have a vast developer base to tap into. If they manage to get the distribution right, control handset variety (or at least require minimum specs; a la PC architecture), tame the carriers and open up to developers just a tad, you will see millions of corporate developers installing the mobile plugins for Visual Studio and cranking out apps. But I am afraid it's not in MS' nature to motivate developers, but have always relied on market demand and other people's $$$ to make their shenanigans palatable to developers. If I was in charge, I would assemble a team of 8 - 12 and write a nice .NET/C# cross-compiler/wrapper given to any registered Windows Mobile developer; even remote, hosted cross compiler. Make people write with your tools first, for your primary platform, with the option to target other platforms from the same source. Apple was afraid of this with the 3.3.1 policy: iOS getting wrapped with Win32 API or Android SDK would have been a nightmare for quality on the iOS. The first tool developer to successfully target top N platforms (for N>2) is gonna rake in cash, 3.3.1 permitting.