this post was submitted on 19 Sep 2023
134 points (98.6% liked)

Games

16729 readers
686 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago
MODERATORS
 

A statement from a Google employee, Dov Zimring, has been released as a part of the FTC vs Microsoft court case (via 9to5Google). Only minorly redacted, the statement gives us a run down of Google's position leading up to Stadia's closure and why, ultimately, Stadia was in a death spiral long before its actual demise.

"For Stadia to succeed, both consumers and publishers needed to find sufficient value in the Stadia platform. Stadia conducted user experience research on the reasons why gamers choose one platform over another. That research showed that the primary reasons why gamers choose a game platform are (1) content catalog (breadth and depth) and (2) network effects (where their friends play).

...

"However, Stadia never had access to the extensive library of games available on Xbox, PlayStation, and Steam. More importantly, these competing services offered a wider selection of AAA games than Stadia," Zimring says.

According to the statement, Google would also offer to pay some, or all, of the costs associated with porting a game to Stadia's Linux-based streaming platform to try and get more games on the platform. Still, in Google's eyes, this wasn't enough to compete with easier platforms to develop for, such as Nvidia's GeForce Now.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 52 points 1 year ago (27 children)

The worst thing about Stadia was the squandered opportunities. Had Google actually put some effort into marketing it, it could have really succeeded. The tech behind it worked amazingly well. I played Destiny 2 on it from launch to the service's shutdown, and it was a fantastic experience. The latency was nowhere near as bad as people (who often never even tried the platform) would claim, and it was also the best place to play Cyberpunk 2077 at launch, as it was somehow the most stable version of the game. Streaming to YouTube worked very well, and some of the integrated features with YouTube (where viewers could interact with certain games) were also kinda groundbreaking.

But somehow, Google couldn't be bothered to advertise the product at all. They ran 1 Super Bowl commercial which didn't make a whole lot of sense to the average viewer, and then basically zero marketing after that. They refused to inform the public about what the product is or how it worked or what stood it apart from its competition, which led to bad-faith reviews and rumors being spread about the platform, ultimately leading to most people who knew about Stadia being wildly misinformed on it.

It's such a shame. I absolutely loved Stadia. It fit my needs perfectly. None of the other streaming platforms I've tried have even come close, even today.

[โ€“] [email protected] 2 points 1 year ago

Google couldn't be bothered to advertise the product at all. Except, apparently, to me specifically. I must have seen the same handful of Stadia advertisements literally 100+ times while watching YouTube. I got very sick of it after a certain point.

load more comments (26 replies)