AI is a topic that often stirs debate, yet it has become a constant presence in our lives, much like an essential app on our smartphones. I find myself using it almost daily now, and it’s not just because Microsoft seems determined to integrate it into every product they roll out.
From the introduction of ChatGPT to the evolution of Bing Chat into what is now known as Copilot, I’ve discovered enjoyable ways to weave AI technology into my everyday routines.
On paper, the announcement of Xbox Copilot (officially called Copilot for Gaming) by Microsoft seems promising. The sticking point, for me, is having to use my phone to interact with it. The last thing I want to do is fiddle with my phone while I’m in the middle of a gaming session.
Remember the Kinect? That intriguing piece of hardware from Microsoft that seemed to be ahead of its time but ultimately ended up on the scrap heap? Imagine pairing Kinect with Xbox Copilot—tell me that wouldn’t be the best way to go about it?
Let’s talk about voice interaction on the same device versus needing a phone.
The second-generation Kinect launched at what was arguably the wrong time. The version for the Xbox 360 was a quirky addition that offered innovative ways to engage with games. When the Xbox One came out, Kinect became your trusty voice-activated sidekick.
I have fond memories of using voice commands with my Xbox One through Kinect. What started as a novelty for turning the console on and off became an incredibly useful tool.
As a new parent, being able to navigate TV and media with a baby in my arms thanks to Kinect was a godsend. Those were the days when my cable box was connected to my Xbox, allowing me to use OneGuide for seamless control.
Fast forward to today, AI is swiftly becoming an indispensable tool, and Microsoft is pushing it into every corner of tech. Am I the only one who thinks a native Copilot on the Xbox console, with Kinect integration, would have been fantastic?
Sure, you can use voice commands with your phone, but that’s just adding another device into the mix when you’re already juggling a console, a TV, and a controller. Unless you’ve got extra arms like Otto Octavius, you’re going to end up taking a hand off the controller to use Copilot.
My colleague, Samuel Tolbert, summed it up well when discussing the introduction of Xbox Copilot. He said, “Whether I’m playing solo or chatting with friends, I don’t want to resort to talking to a second, smaller screen for extra features or fun.”
It’s too bad for Kinect now, but the logic behind it is still sound.
At some point, Microsoft might decide to introduce some form of Copilot directly onto the Xbox console. We’ve already seen AI pop up in Notepad on Windows 11, so it wouldn’t be surprising.
The issue lies with the fact that the hardware we once had is no longer available. Even if you still have a Kinect, it’s not compatible with the new generation consoles.
If given the option, I’d love to engage with Copilot on the console, but only through voice interaction. While immersed in a game, the last thing I want is to shift my focus elsewhere. Surely, I’m not alone in that sentiment.
If using an AI chatbot means stepping away from gameplay, it’s destined to flop. To avoid this, voice activation must be part of its functionality. That implies you need a microphone hooked up to the console—without the Kinect, that’s our only option.
It must seamlessly work with voice, for the same reason. You can’t expect players to halt their session just to play with the latest AI gizmo from Microsoft. It should be something you can launch, talk to, and dismiss without missing a beat in your game.
Will we see this come to fruition? It’s hard to tell. But like many things Microsoft has created and then shelved, it leaves us pondering the big “what if?”
