Things Microsoft should fix
This is a kind of pointless thread post of the sort you can find anywhere. Honest truth. Also, it is just my opinion, so feel free to completely ignore it. But here are some of the things I think are either holding Microsoft back, or are less relevant but still poorly executed.
Security in Windows 10:
I still believe everyone is blowing this massively out of proportion. That doesn't mean that Microsoft shouldn't be both more transparent and make it easier to completely disable all privacy concerns. Something like an advanced wizard during the OOBE that takes you through high level features and gives at least 3 options covering; Full privacy, a compromise and full functionality. And make sure that they are presented as such along with what is shared.
I think most people will still just go with defaults. But making the advanced option easy to understand and properly and fully disable would shut up most whiners.
Even better, instead of a default option, give 3 similar defaults, then you don't even need to dive into the longer advanced section to disable.
Patch Notes:
This is the oddest change in behavior at MS in recent times. As others have pointed out thanks to leaks, it isn't like Microsoft isn't generating release notes or somehow doesn't know what is in these builds. They know. They are a massive company with an assload of formal procedures and policy in place. Really don't get why they would leave these out. Seems like an attempt to try and silence the nay-sayers on their auto-update policy. Frankly, I agree with the auto-update policy but still disagree with the lack of patch notes. Should be rectified. This is one of those few things that might help erode their dominance in the enterprise.
One TRUE Windows:
Yes, in short order, pretty much all major Microsoft products will be running the same core (doubt Band does for instance). But they still don't run the same OS. I get it, Win32 apps aren't going to run on ARM any time soon. But then, Microsoft is slowly moving towards killing ARM support anyway. WinRT is dead. All we need know are Intel powered phones. Xbox is already x64. I get it, a console is a different beast than a desktop in terms of privacy, etc... That doesn't mean that I don't want to be able to run my Windows games on my Xbox. Oh! And Vice versa.
Solution: Same OS, different interface with added security, options, etc... for getting at traditional Windows apps. Interface is based on device category and to be authorized for the Console experience the OEM needs to prove performance meets or exceeds XB1 characteristics and they want that interface. BAM! Next gen Xbox console is just a gaming PC.
Insider Program:
I almost wrote this entire article on this topic. Again! Put simply, the damn thing seems borderline schizophrenic. We'll wait months for a build, bitch, and then get several in the span of a few weeks, then things go dark again and the cycle continues. As I've said, I get it, people are abusing it so they are being more cautious. And, as I've said, they should really have publicly posted guidelines for what passes and fails for a particular ring and rough goals for build frequency. Also, higher rings should have increasing requirements (which don't involve working for Microsoft) to enable access to more regular, more unstable builds with fewer guarantees. If they are serious about fielding feedback they need to fix this process.
Scrap Surface Book:
Love the Surface Pro. Loved the concept from day 1. Loving that everyone from OEMs to competitors are finally jumping on board. Surface Book, unlike Surface Pro, doesn't really bring a new category to life or do anything major to fix any issues with competitors similar offerings. At the prices they are asking and assuming more constrained production runs it should be a success and profitable. That doesn't mean that they should do it. If no one was doing detachables or at least no one doing them right, then this would have a place.
Murder Windows Phone:
I LOVE Windows Phone. But, Microsoft and Nokia have left the damn thing on life support and someone needs to pull the plug. As hinted above, not suggesting exiting mobile. Replace Windows 10 Mobile with Windows 10. Like the Xbox suggestions, there are some implications and obviously UI differences which can be locked behind a device type. In fact, go back in time, kill Surface Book before its launched and do an x86 phone instead. Promise 2 years UWP app compatibility to Windows Phone 8.1 users and be done with it. The Lumia 950 and XL variant look like good phones, but as I've said before they are about a year or more too late on delivering a new flagship device.
Hololens for the masses:
FIX THE FoV!!!!!! $3K for a developer kit is pretty steep. But guess what? Competition is already brewing and regular consumers will buy the dev kit and trash talk the FoV anyway. As I've said in the past, give up on untethered if that is what it takes. Produce a unit with the largest FoV possible and make whatever concessions you need to. Frankly, for a 1st gen product there really won't be a ton of stuff that truly utilizes it in an untethered fashion anyway. So, just fucking make it and get whatever money to help fund phase 2 ASAP.
So, there you have it. A few thoughts on things Microsoft could improve on.
Security in Windows 10:
I still believe everyone is blowing this massively out of proportion. That doesn't mean that Microsoft shouldn't be both more transparent and make it easier to completely disable all privacy concerns. Something like an advanced wizard during the OOBE that takes you through high level features and gives at least 3 options covering; Full privacy, a compromise and full functionality. And make sure that they are presented as such along with what is shared.
I think most people will still just go with defaults. But making the advanced option easy to understand and properly and fully disable would shut up most whiners.
Even better, instead of a default option, give 3 similar defaults, then you don't even need to dive into the longer advanced section to disable.
Patch Notes:
This is the oddest change in behavior at MS in recent times. As others have pointed out thanks to leaks, it isn't like Microsoft isn't generating release notes or somehow doesn't know what is in these builds. They know. They are a massive company with an assload of formal procedures and policy in place. Really don't get why they would leave these out. Seems like an attempt to try and silence the nay-sayers on their auto-update policy. Frankly, I agree with the auto-update policy but still disagree with the lack of patch notes. Should be rectified. This is one of those few things that might help erode their dominance in the enterprise.
One TRUE Windows:
Yes, in short order, pretty much all major Microsoft products will be running the same core (doubt Band does for instance). But they still don't run the same OS. I get it, Win32 apps aren't going to run on ARM any time soon. But then, Microsoft is slowly moving towards killing ARM support anyway. WinRT is dead. All we need know are Intel powered phones. Xbox is already x64. I get it, a console is a different beast than a desktop in terms of privacy, etc... That doesn't mean that I don't want to be able to run my Windows games on my Xbox. Oh! And Vice versa.
Solution: Same OS, different interface with added security, options, etc... for getting at traditional Windows apps. Interface is based on device category and to be authorized for the Console experience the OEM needs to prove performance meets or exceeds XB1 characteristics and they want that interface. BAM! Next gen Xbox console is just a gaming PC.
Insider Program:
I almost wrote this entire article on this topic. Again! Put simply, the damn thing seems borderline schizophrenic. We'll wait months for a build, bitch, and then get several in the span of a few weeks, then things go dark again and the cycle continues. As I've said, I get it, people are abusing it so they are being more cautious. And, as I've said, they should really have publicly posted guidelines for what passes and fails for a particular ring and rough goals for build frequency. Also, higher rings should have increasing requirements (which don't involve working for Microsoft) to enable access to more regular, more unstable builds with fewer guarantees. If they are serious about fielding feedback they need to fix this process.
Scrap Surface Book:
Love the Surface Pro. Loved the concept from day 1. Loving that everyone from OEMs to competitors are finally jumping on board. Surface Book, unlike Surface Pro, doesn't really bring a new category to life or do anything major to fix any issues with competitors similar offerings. At the prices they are asking and assuming more constrained production runs it should be a success and profitable. That doesn't mean that they should do it. If no one was doing detachables or at least no one doing them right, then this would have a place.
Murder Windows Phone:
I LOVE Windows Phone. But, Microsoft and Nokia have left the damn thing on life support and someone needs to pull the plug. As hinted above, not suggesting exiting mobile. Replace Windows 10 Mobile with Windows 10. Like the Xbox suggestions, there are some implications and obviously UI differences which can be locked behind a device type. In fact, go back in time, kill Surface Book before its launched and do an x86 phone instead. Promise 2 years UWP app compatibility to Windows Phone 8.1 users and be done with it. The Lumia 950 and XL variant look like good phones, but as I've said before they are about a year or more too late on delivering a new flagship device.
Hololens for the masses:
FIX THE FoV!!!!!! $3K for a developer kit is pretty steep. But guess what? Competition is already brewing and regular consumers will buy the dev kit and trash talk the FoV anyway. As I've said in the past, give up on untethered if that is what it takes. Produce a unit with the largest FoV possible and make whatever concessions you need to. Frankly, for a 1st gen product there really won't be a ton of stuff that truly utilizes it in an untethered fashion anyway. So, just fucking make it and get whatever money to help fund phase 2 ASAP.
So, there you have it. A few thoughts on things Microsoft could improve on.
Comments
Post a Comment