Windows Blue issues for Enterprise users:
Last week I was really ecstatic about the leaked information from Redmond on Windows Blue. I went ahead and shared my excitement in my post “Windows Blue – top 10 reasons for Microsoft’s new OS in the works!“. I just couldn’t stop thinking about all the positives for the end consumer till I turned my thoughts to what it means for Enterprise users. Here are some of my quick thoughts on why Windows Blue may not be a hit with Enterprises and the overstretched IT department!
- Shorter/yearly release cycles means not enough time for Enterprises to do the rigorous testing before a new deployment across the enterprise
- More frequent disruptions to the business with each Enterprise roll-out
- More support desk tickets in any given year due to a yearly rollout schedule
- More frequent training required for the Enterprise end user
- Building applications for the Microsoft marketplace is going to be more tedious; you’ve now got to build it to support Windows 8 RT, Windows 8, and Windows Blue
- Once the Windows SDK gets updated to support Windows Blue, Microsoft will stop accepting apps that are built only for Windows 8 (for obvious reasons)
Windows Blue – Bad news for developers?
It is also bad news for developers and is something that may not benefit Microsoft – probably cause them more harm if you ask me. Given that there is a shortage of Apps for the Microsoft mobile device market, which was promised to be remedied by support to the software community with the release of Windows 8, the worst thing Microsoft could do to discourage them is leak news of a new platform! Microsoft just cannot afford a “wait and see” attitude among its dwindling community of mobile app developers.
Let’s hope Microsoft has a separate strategy for the Enterprise when it comes to Windows Blue.