Is Windows Phone moving to the Windows org?

ms org chart cartoonToday, in a blog post she called “As the Microsoft Windows Phone org churns”, while noting the transfer of Windows Phone GM Matt Bencke to Xbox Live, Mary Jo Foley coined a new phrase, only half jokingly aligning herself, a la the Occupy Wall Street movement, as one of the “1.5%”:

As I’ve blogged and said repeatedly this year, I am a Windows Phone fan. (Yep, I’m one of the 1.5 percent.) I really hope Microsoft doesn’t relegate WP to nothing but a complement to Windows, in terms of its positioning and marketing. But if Microsoft and partners can’t grow Windows Phone share in a very substantial way in the next few months, maybe this is Plan B… (?)

The departure of Bencke follows the recent “benching” of Windows Phone President Andy Lees in favor of Terry Meyerson, a move some are positioning as a precursor to an org move that would bring Windows Phone (presumably powered by a “MinWin” Windows 8 core), into the Windows org, run by President Steven Sinofsky.

So will Windows Phone become a Sinofsky phone?  We’re not so sure.  For one thing, Mary Jo points out that she’s hearing the marketing efforts for Windows Phone and Windows may indeed merge, but not the (development) orgs themselves.

While we do believe that Windows Phone will run a “MinWin” core (and sooner rather than later, as Nokia will be insistent on a next gen set of capabilities to sell next holiday season), and we even think that the same treatment may come soon, too, to Xbox, building on the emphasis of the Xbox/Kinect/Bing triumvirate as Microsoft’s version of a smart TV controller.  We strongly doubt, however, that Xbox would become part of the Windows org.  That would be 1/3 of the “3 screens” strategy outside of the Windows org already, and there’s not much reason to believe that moving fast paced consumer facing smartphone development into the sometimes (ok, always) slow and plodding Windows org would make much sense.

What Windows would control would be the “MinWin” core that Windows 8, Windows 8 Server, Windows 8 tablets, and in this scenario Windows Phone and Xbox, would all “share”.  All roads would still lead to Sinofsky, with a central Windows developer team powering essentially everything Microsoft makes.

And while there are basic differences between each of the 3 screens that go beyond just the screen size, there could be lots of common ground in terms of apps management and parts of the OS outside the core that would be re-usable between devices, again controlled centrally, most probably by the Windows org.

Just about everything we’ve heard or read in the past year or so has been pointing to this single central OS core running all 3 screens (phone, PC, and TV), but the power of the concept could be in differentiating and expanding each of those screen’s capabilities somewhat separately while still centrally maintaining a safe, solid, and up to date core.

Sounds good to us, but what do we know?  We’re just one of the 1.5%, after all.

Comments

  • Anonymous

    There are very big benefits to combining Windows Phone and Windows 8 from a development perspective. They will soon run on similar hardware and have similar hardware functionality requirements. Why recreate the wheel for each platform?

    But… they need to keep the interface teams and development cycles separate. The mobile phone space moves much quicker and the confined space of the interface needs to be thought of differently. If they merge the two teams, they need to realize that the two systems have different life cycles that needs to be taken into account.

  • Guest

    It makes sense to have them under one org. But at this point is it going to matter? MS isn’t agile enough to compete successfully anymore.  It’s not like we can say the phone group underestimated iPhone and took three years to respond but the Windows group would never do that. They did just that, only with iPad. So it’s not division specific, it’s company-wide.

    I see 2012 being a very rough year for MS and the beginning of a long term financial decline (the relevance part started a long time ago). They’ve simply missed too many opportunities and are no longer well positioned relative to Apple or Google. I also think Ballmer will finally be out in 2012. Once growth goes, even Bill won’t be able to save him any longer.

  • Mmmm

    All these rumors of potential platform changes aren’t doing any good of developer esteem. Unlike iOS or Android, where you can at least know that you can still develop with the same techniques and methods over time, Microsoft cannot settle on one framework.

    If they fold WP7 into W8, I’m afraid we have to suffer yet another seismic shift experienced in transition from WM6 to WP7. First they got all WP7 developers on board for Silverlight, and the next moment Windows 8 is going to be… HTML5? The inconsistency and having to relearn everything all over again and again is simply insane.

    Besides, at this point, the UI framework of Windows 8 is still much weaker than WP7. There are no specific guidelines for how things should be laid out, unlike Pivot and Panorama of WP7. All we got so far is the gigantic button approach in W8: the big rectangles that essentially makes everyone slam on the Music Beta app. WP7 is way more polished at this point and it would be a shame to fold it into W8 which is still very rough around edges.