Microsoft got into the mobile market early with Pocket PC devices. Launched in 2000, these were devices aimed at professionals who wanted mobile access to their work-related calendars and email. With dominance in enterprise software, Microsoft was well positioned to sell . Apple’s release of the iPhone in 2007 completely changed that market though.
In order to compete with the iPhone, Microsoft decided to entirely rework Windows Mobile into Windows Phone. It would have a new touch-focused interface and an application model much closer to that offered by the iPhone.
The Silverlight code base ended up being chosen as the basis for applications on Windows Phone. Some of the Silverlight team supported that effort for the Windows Phone 7 release. Then with Silverlight’s wind down as browser plugins became obsolete, I moved over to working on the Windows Phone development platform for Windows Phone 8 in late 2011.
For Windows Phone 8, the big challenge was a move from being based on Windows CE to Windows NT. This brought in a lot of OS capabilities, but it also had the potential to break a lot of things. My work for the release ended up being documenting the places where app developers had taken dependencies on the ordering of events on Windows Phone 7 and then adding code to the platform so that those events would be guaranteed to have the same ordering when the apps ran on Windows Phone 8. It wasn’t particularly exciting work, but it was critical to maintaining compatibility with the existing Windows Phone app catalog.
After Windows Phone 8 shipped, I changed roles for the Windows Phone 8.1 release. I moved from being a individual contributor to being a team lead, and I left the app platform team for the team responsible for the phone browser’s user interface. My team’s goal was to make Internet Explorer on Windows Phone feel modern. We implemented support for having more than 6 open tabs, for gesture navigation, roaming favorites and history across Windows devices, and autocomplete for the address bar. I had been an acting lead for a while during Windows Phone 8, but this was my first time officially being a manager. I thought my team was great, and we accomplished a lot for the release.
Across this time, Windows Phone was a fun project to work on and a product that I was proud of. It had a lot of innovative features like live tiles, jump lists, kids corner, and more. Unfortunately, it was also struggling in the market. By the time Microsoft shifted from an enterprise focus to a consumer focus for smartphones, iPhone and Android were both already in the market. This meant that for app developers, it would be a third mobile OS to support. Then missteps in the move from earlier phone projects, Windows Mobile and Kin, as well as not allowing devices to update from Windows Phone 7 to Windows Phone 8 caused frustrations amongst mobile operators, fans, app developers, and device manufacturers.
There had also been a problem with the organization of Microsoft’s operating system teams. When the Windows 8 project started, one of its goals was to support tablets and compete with the iPad. Unfortunately, upper management on the Windows side decided that aligning with the Windows Phone application model would only hold Windows back, so they built an entirely different application model than what the Windows Phone team had been using since the release of Windows Phone 7. This meant that applications written for Windows Phone wouldn’t run on Windows tablets and vice-versa. This set the company on a path where the development platforms and app stores for both Windows and Windows Phone were weaker offerings than they otherwise could have been.
After the relative failure of Windows 8 and 8.1 to draw fans or app developers and the continuing struggles of Windows Phone to build market share, Microsoft decided to merge the Windows and Windows Phone projects into a single team for Windows 10. The idea was that a unified platform would improve the odds of success for both, but a lot of ground had already been lost over the years of them pursuing their own directions. The idea of a unified Windows platform offered some hope internally, and at the time, I was happy to see the teams merging together.
When the reorganization happened in 2014, I, along with most of my reports from the phone browser team, moved to a new team that was tasked with building a browser app for Windows and Windows Phone. My next career post will cover my time on that team.