The downfall of Windows on phones is a tale that has been told and retold by observers, enthusiasts and Microsoft haters time and again.
Though Windows 10 Mobile's demise is undeniable, Microsoft's mobile strategy has arguably always included a transition from a mobile OS on phone hardware to full Windows on context-conforming Pocket PCs. That vision is materializing as Windows Core OS and Microsoft's rumored "Project Andromeda" story unfold.
Had Windows phone succeeded, Microsoft would have likely still pursued the post-smartphone pocket PC vision it's currently pursuing. It's a natural evolution of connected computing and a realization of the company's decades-old goal of bringing full Windows to pocketable hardware.
It's within this context of what could have been and what may yet be, that exiting Windows Chief Terry Myerson and former Developers Relations Head for Windows Phone Brandon Watson have shared their thoughts on why Windows on phone, not Windows on mobile, failed.
Microsoft staffers on Windows phone's failure
Myerson, who's leaving Microsoft and who once led Windows phone efforts, shared his experiences on LinkedIn:
I knew we had so much work to do on our non-touch no-app-store Windows Mobile effort. I was honored, and more than a little terrified. The Windows Phone experience was incredibly challenging.
In response to the challenge, Microsoft innovated in phone user experiences, with Live tiles, social network integration, Hubs, Rooms, and the fluidity of the OS. Still, Myerson said Windows phone failed because:
- Early Windows phones were founded on an incomplete Windows CE platform, designed for small embedded systems.
- The industry moved forward faster than Microsoft could keep pace.
- Android presented an enormous disruption in the business model.
Watson added insufficient OEM and carrier support to that list of reason for failure:
The argument that Microsoft isn't investing in mobile, because it gave up on smartphones, is an erroneous assessment. A mobile device doesn't have to be asmartphone, though a smartphone is a mobile device. This point must be understood before you can grasp how Microsoft's mobile investments and Project Andromeda may address the challenges that contributed to Windows on phone failures.
Incomplete Windows CE foundation
Incomplete Windows CE limited Microsoft's ability to bring the power and versatility of Windows to a mobile form factor.
OneCore unifies Windows across form factors, and Core OS enables a context-sensitive OS that conforms to device types and device states. Microsoft's rumored Project Andromeda's OS will potentially shift between mobile, tablet and desktop modes seamlessly.
Industry moved faster than Microsoft could catch up
Apple and Google had developed carrier, developer, customer and OEM (Android) relationships years before Windows Phone 7 arrived.
As connected computing becomes increasingly demanding and the slate-shaped smartphone market stagnates, Always Connected PCs and subsequent Project Andromeda-inspired OEM devices may be Microsoft's and Qualcomm's preemptive step into the next phase of connected computing.
Android's disruptive business model and caring for carriers
Though Myerson doesn't identify Android's "disruptive" business model, he may have been referring to the OS as free and customizable for OEM partners.
Microsoft ultimately made Windows free to OEMs on smaller devices. Additionally, Core OS lets OEMs include only the Windows features they want on their devices. Windows 10's breadth of features from inking, gaming, mixed reality and more combined with creative OEM hardware may inspire PC and smartphone makers to embrace Andromeda-inspired devices.
Furthermore, always-connected devices will allow consumers to buy data from the Microsoft Store and switch between carriers almost on the fly. This gives carriers an incentive to carry cellular PCs to make their data and voice packages more competitive.
The notorious app gap
Microsoft is collaborating with Google on Progressive Web Apps (PWA) and is treating them as native apps in Windows 10. Simply, put these app-web hybrids will behave as native Universal Windows Platform (UWP) apps.
Using a web crawler, Microsoft has begun to slowly populate the Microsoft Store by merely pulling PWAs into the Store PWAs. Furthermore, PWAs are easier to build, maintain and are cross-platform.
No guarantees but it's a plan
Microsoft appears to have a mobile plan that addresses the issues that doomed Windows on phone. No one knows how this will play out, but past failures don't dictate future outcomes.