Microsoft execs speak about how they dealt with feedback for Windows 10, unifying platforms
Tom Warren / The Verge :
Context & Ripple Effects
This interview sits at the start of a decade-long arc in how Microsoft organizes Windows. In July 2015, with Windows 10 shipping as 'Windows as a service', execs are selling the idea of one platform across PC, phone, and Xbox, built around absorbing user feedback rather than the fragmented release cadence that defined the Windows 8 era.
That unification promise proved hard to hold: by 2019 Microsoft was still trying to undo the divide between UWP and Win32, and the same year it conceded defeat on a homegrown browser engine with the decision to rebuild Edge on Chromium. The 2018 org split that scattered Windows engineering was only reversed in September 2025, when an internal memo put key Windows teams back under Pavan Davuluri — making this 2015 conversation a useful baseline for how often Microsoft has re-litigated this exact question.
First-order effects
- Windows Insiders and early adopters become a formal part of the product process, with Microsoft publicly crediting their feedback for changes to Windows 10 rather than shipping fixed annual releases.
- Developers hear that UWP is the path to reaching every Microsoft device class from one codebase, setting expectations for the app store strategy Kevin Gallo would later have to walk back.
Second-order effects
- Terry Myerson's combined Windows-and-Devices organization gets the mandate to make hardware (Surface, phones) and OS decisions together — the structure whose later split Panay-era coverage and the 2025 reunification both react against.
- When the one-platform promise strains, rivals' ecosystems fill the gap: the Chromium Edge decision shows Microsoft adopting competitors' foundations where unifying its own had failed.
Third-order effects
- If the pattern holds, Microsoft's platform strategy oscillates between centralization and fragmentation roughly every few years — the 2018 split, the 2025 Davuluri reunification, and the Copilot app merger all being instances of the same cycle.
- Developer trust becomes the durable constraint: each reversal of the unify-then-split cycle raises the cost of asking the ecosystem to bet again on a single Windows platform.
The trend: Microsoft has spent a decade cycling between splitting and re-unifying Windows engineering, and the 2015 one-platform pitch is the first data point in that recurring debate.