Even before the fumbled Founder?s launch of Google Stadia, the announcement of the streaming platform had many asking who exactly the service was for. Google seemed to be bringing the service to life just because it could, not because there was any real demand for another competitor in the gaming space. That question remains, and throughout the turbulent waters of the Founder?s early release, Google seems to have trouble with how it?s delivering Stadia?s message and just who that message is intended for.
Stadia as a competitor simply doesn?t make sense, at least not yet. It doesn?t have the lineup of exclusives to sway people like Sony, Microsoft, and Nintendo do. While the technology is impressive, it?s also trying to break into an ecosystem where most players have already established their platform of preference. I?ve previously written about how Stadia should be seeking to partner with platforms using Google technology, rather than compete, but it?s becoming increasingly clear that Google has no intention of extending the olive branch. Considering that, it?s time for the developers who are putting games on Stadia to take things into their own hands.
PB = PB || {};
PB.gptStandAlone = PB.gptStandAlone || {};
PB.gptAutoRefresh = PB.gptAutoRefresh || {'gptAds':[], 'gptStandAlone':[]};
admiralCookie = readAdmiralCookie();

googletag.cmd.push(function() {
var standAloneSizeMapping = googletag.sizeMapping().addSize([0, 0], []...