Microsoft talks Windows Phone 7 Series development ahead of GDC: Silverlight, XNA, and no backward compatibility
Microsoft is keen on unveiling the meat of its developer story around Windows Phone 7 Series at MIX10 in less than two weeks, but with GDC coming up next week …
Context & Ripple Effects
Microsoft has confirmed the shape of its Windows Phone 7 Series developer story ahead of next week's Game Developers Conference: Silverlight and XNA as the supported stacks, with the full strategy to be unveiled at MIX10 — and, notably, no backward compatibility with the existing Windows Mobile base. Charlie Kindel's same-day post 'Different Means Better' frames the clean break as deliberate rather than an accident of the rewrite.
That framing matters because the compatibility decision cuts both ways: legacy Windows Mobile developers lose their upgrade path outright, while the large Silverlight and XNA communities gain a brand-new mobile target two weeks before Microsoft formally pitches them at MIX10.
First-order effects
- Existing Windows Mobile application developers are cut off — apps built on the current platform will not carry over to 7 Series, forcing a rebuild decision on Microsoft's own installed developer base.
- Silverlight and XNA developers get a new device category to target immediately, with Microsoft using GDC and then MIX10 to recruit them before the platform ships.
Second-order effects
- Game studios already invested in XNA tooling face a low-friction porting path to the phone, pulling mobile into the same toolchain Microsoft uses elsewhere — and pressuring competing mobile platforms' developer pitches at exactly the moment 7 Series goes recruiting.
- OEMs and carriers building 7 Series devices inherit a curated, from-scratch app story instead of a legacy catalog, making developer adoption — not hardware specs — the bottleneck metric for the launch.
Third-order effects
- If the pattern holds, Microsoft consolidates its consumer-device development around one managed runtime family (Silverlight/XNA) rather than native code per device class, structurally repositioning Windows Phone as an extension of its broader developer ecosystem rather than a standalone mobile OS.
- A platform willing to orphan its installed base to restart on modern tooling sets a precedent rivals may have to match — trading continuity for a cleaner developer experience becomes a legitimate competitive move rather than a liability.
The trend: Mobile platform competition is shifting from hardware differentiation to control of the developer toolchain, with Microsoft betting its restart on a unified managed-runtime stack.