Microsoft reportedly winding down development on some apps that ship with Windows 10
Developers working on some of Microsoft's built-in apps are being pushed to work on Edge instead, according to a new report.
Microsoft recently announced a major internal reorganization effort, shifting teams around, breaking up the Windows Devices Group and leading to the departure of its chief, Terry Myerson. According to a new report, however, the shakeup is having an impact on the teams behind at least some of Microsoft's apps that ship with Windows 10.
Thurrott's Brad Sams reports that Microsoft is tapering off development behind "several" of Windows 10's included apps. It's unclear exactly which apps will be impacted, but it's easy to see how something like News or Weather, whose functions can be easily replicated on the web, could be on the chopping block.
According to Sams, developers who are working on these apps are being offered positions to work on the Microsoft Edge team, potentially along with developers from other areas.
Given Microsoft's focus on Progressive Web Apps going forward (the first batch began hitting the Microsoft Store last week), the timing would make sense, particularly if we begin to see an influx of automatically indexed PWAs that can replicate the same functions of Microsoft's built-in apps. However, what that means for apps like Mail and Calendar, which likely sees more use than something like the Weather app, is unclear.
Windows Central Newsletter
Get the best of Windows Central in your inbox, every day!
Dan Thorp-Lancaster is the former Editor-in-Chief of Windows Central. He began working with Windows Central, Android Central, and iMore as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl.
OK, what did I miss? You told me that MSFT was simply "retrenching" in the mobile phone marketplace ... and now you're telling me that they "failed"??? It was all in Nadella's infamous 2014 memo. I had a WinPRT80 app that users loved (and was better than the iOS and Android competitors) but, guess what, it remained a WinPRT80 app because MSFT kept screwing around with the APIs. Just modifying it to WinPRT81 would have required a lot of work and sales were dismal. All work and no pay makes developers unhappy! If I had to choose only one thing that signified MSFT's incompetence in mobile design, from a dev's perspective, it would be the implementation of the ability to select a file in WinPRT81. You had to prepare your app to be shut down and restarted to just get the freaking selected filename!?! The Async fetish was bad enough but that one took the cake (the people who designed that should have been fired and never allowed near a computer again). Even MSFT people on podcasts at later Build conferences laughed at the design. It was that bad.