> I'm someone who lives abroad and doesn't like hunkering down with any equipment, not even a bookcase. I don't like staying in one apartment for a long time. T

> I'm someone who lives abroad and doesn't like hunkering down with any equipment, not even a bookcase. I don't like staying in one apartment for a long time. The only cooking appliance I own is a single cast iron skillet. Something like Stadia interests me if it can deliver. But that's the rub innit? The only people who are going to be really interested in this product are the hypermobile, and I don't know about your experience with mobile internet, but my LTE can barely keep a YouTube video in decent quality going. With remote gaming, you're now adding controller input to that datastream, outbound, and then rendering those actions and transmitting back to the device to enable anything remotely approaching a good gaming experience seems like science fiction. The people who will be most interested in this are those without a "home" setup, and the less "home" you have, the more appealing, but also seems like it would in turn be the most frustrating experience to try and use. Which is sort of what this piece is getting at: - Gamers don't want it, because we already have our libraries and such tuned to existing platforms and devices - Casual gamers may want it, but they're already spoiled for choice in a massive mobile market, where games just happen on their already very powerful phones This puts Stadia in an awkward position of in theory being the worst of both worlds: the limitations of console, with the network requirements only high tier residential internet can deliver, over devices with limited network capability.