Buggy Xbox One preview should have been expected...
A number of sites are jumping on the bandwagon and pointing out that the latest preview version of the Xbox One (the new experience, AKA the Windows 10 based version) is incredibly buggy. But, when you consider how this beta was handled, it really isn't interesting in the slightest or even newsworthy. Shame on the click-bait articles that are either failing to acknowledge the circumstances or only briefly mentioning them in passing!
This IS NOT like the Windows 10 or Phone Insider builds. And even those went out with numerous warnings through the official channels. But, by contrast, they were open immediately to pretty much everyone and "un-official" channels (by which I mean MS employees saying things not necessarily PR sanctioned) either kept quiet or encouraged people to use them.
With the Xbox One, things have been markedly different. Lets start with those allowed in to this initial release. It is just a subset of existing Preview members, and specifically a subset which includes their most active for providing feedback. That alone should say everything. But, on top of that, even to THAT group of users, both official and unofficial advice has basically been "use at own risk".
In other words... this preview is basically a super privileged, super early access, but even still, actually enrolling at this stage of the game is CLEARLY marked as having a high risk factor associated with it. I can say this because, I am one of those invited. And I can tell you, it is MUCH clearer in this Preview program than any others that things don't just have the potential to go wrong, but that they more than likely WILL.
Microsoft did one of the sorts of things I had hoped they would do (and had blogged about here) regarding even rougher, earlier previews out. They used a barrier for entry which people couldn't ignore or artificially circumvent after the fact. It required a history of participation and actually using the preview program for its intended purpose. Which is, of course, to have people not just use the pre-release software, but to also proactively assist by reporting bugs and providing feedback. Once the requirements were posted, it was effectively impossible to go from a score of zero to one which would get you on the list.
And, as both an avid pre-release software user, and someone interested in supplying feedback, I can also say that the warnings were sufficient to give me enough pause that it seems like I missed out on the first wave. I tried switching my enrollment status yesterday, but it is still pending. And I assume that it will stay that way now until the second update.
Side note: If I did miss the first wave now, I'm both pleased and disappointed. As said, I knew this would be a riskier beta and didn't want it screwing anything over. Disappointed that I missed out nonetheless. But in no way would I be mad or upset over it. This IS the right way to include the public in such an early release.
Anyone who blindly accepted and installed it and is now complaining really has no grounds to do so. But, I don't think that is the bulk of what is going on. The people spreading FUD are generally those reading reports of what isn't working who happen to write for online blogs. The people providing the data are likely just making sure Microsoft and others are aware of what issues are present so that they A) get fixed and B) other people who need those features don't waste time jumping onboard until they're fixed.
I just want to repeat this again... this is CLEARLY a very rough build. And Microsoft has, for once, successfully marketed it as such. Again and again. And even fenced the vast majority of users out of even trying it. So, it isn't news that it is buggy.
This IS NOT like the Windows 10 or Phone Insider builds. And even those went out with numerous warnings through the official channels. But, by contrast, they were open immediately to pretty much everyone and "un-official" channels (by which I mean MS employees saying things not necessarily PR sanctioned) either kept quiet or encouraged people to use them.
With the Xbox One, things have been markedly different. Lets start with those allowed in to this initial release. It is just a subset of existing Preview members, and specifically a subset which includes their most active for providing feedback. That alone should say everything. But, on top of that, even to THAT group of users, both official and unofficial advice has basically been "use at own risk".
In other words... this preview is basically a super privileged, super early access, but even still, actually enrolling at this stage of the game is CLEARLY marked as having a high risk factor associated with it. I can say this because, I am one of those invited. And I can tell you, it is MUCH clearer in this Preview program than any others that things don't just have the potential to go wrong, but that they more than likely WILL.
Microsoft did one of the sorts of things I had hoped they would do (and had blogged about here) regarding even rougher, earlier previews out. They used a barrier for entry which people couldn't ignore or artificially circumvent after the fact. It required a history of participation and actually using the preview program for its intended purpose. Which is, of course, to have people not just use the pre-release software, but to also proactively assist by reporting bugs and providing feedback. Once the requirements were posted, it was effectively impossible to go from a score of zero to one which would get you on the list.
And, as both an avid pre-release software user, and someone interested in supplying feedback, I can also say that the warnings were sufficient to give me enough pause that it seems like I missed out on the first wave. I tried switching my enrollment status yesterday, but it is still pending. And I assume that it will stay that way now until the second update.
Side note: If I did miss the first wave now, I'm both pleased and disappointed. As said, I knew this would be a riskier beta and didn't want it screwing anything over. Disappointed that I missed out nonetheless. But in no way would I be mad or upset over it. This IS the right way to include the public in such an early release.
Anyone who blindly accepted and installed it and is now complaining really has no grounds to do so. But, I don't think that is the bulk of what is going on. The people spreading FUD are generally those reading reports of what isn't working who happen to write for online blogs. The people providing the data are likely just making sure Microsoft and others are aware of what issues are present so that they A) get fixed and B) other people who need those features don't waste time jumping onboard until they're fixed.
I just want to repeat this again... this is CLEARLY a very rough build. And Microsoft has, for once, successfully marketed it as such. Again and again. And even fenced the vast majority of users out of even trying it. So, it isn't news that it is buggy.
Comments
Post a Comment