I was a big fan of daydream and unlike Google's other cancellations, this really felt like self sabotage. I don't know why they spent so much R&D on this project and not actively promote or support it (outside of that one big conference)
I would love to see this thing deemed as a troll post in Stadia threads, because it is always, always take out of context and spreads a whole lot of FUD. Half of what's in there was rolled into something else and the rest was either closed because of lack of use or duplicated function (or rebranding). Nexus was not "killed" it was evolved into Pixel, for instance.Killed by Google
Killed by Google is the open source list of dead Google products, services, and devices. It serves as a tribute and memorial of beloved services and products killed by Google.killedbygoogle.com
I was a big fan of daydream and unlike Google's other cancellations, this really felt like self sabotage. I don't know why they spent so much R&D on this project and not actively promote or support it (outside of that one big conference)
LOL! Amazing.Hey, let's talk about another feature of daydream that they never advertised that is honestly amazing: cardboard 6DOF support. Since Daydream natively does 6DOF positional tracking (if it's enabled on your device, which, in google's stupidity, they never did for most devices), and since it's backwards compatible with cardboard, they had an option in the developer's menu to turn any google cardboard, 3DOF app, into a full positionally tracked, 6DOF app:
It's hidden in a developer's menu, where you can enable all sorts of really insane tech in Daydream that was never publicly pushed. For example, Daydream can do unlimited, boundless tracking. This is disabled by default, as a safety procaution. In the dev menu, you can turn it off, and thus it'll turn off the boundry options, which turns Daydream into a full roomscale unit. Other neat shit in this dev menu: AR mode, pass through mode, HUD mode, app recording mode, broadcasting mode (i.e. mirror your daydream output to chromecast). This is where the "enable positional tracking in older cardboard apps" option is found.
To get to this menu, you literally have to enter a secret code on a random screen in the menu's setting. I can't remember the code off hand, but it's something like "highlight build version, then press down 4 times, then the button 4 times, then move up to android version, press the button 4 times, then press up, then down, and a new menu appears" or something like that.
Mind bogglingly stupid how google handled daydream.
The Albatross did that and did it very well four months ago.I would love to see this thing deemed as a troll post in Stadia threads, because it is always, always take out of context and spreads a whole lot of FUD. Half of what's in there was rolled into something else and the rest was either closed because of lack of use or duplicated function (or rebranding). Nexus was not "killed" it was evolved into Pixel, for instance.
I keep quoting this in different Stadia threads because it's a great post, but very few people bother to read it, and fewer still bother to actually think about it. It must be more satisfying to dogpile with moronic "hurr durr this is DOA; this is Google+ all over again; something something Google Reader" posts.This is not a rebuttal to that person's point.
The Google Graveyard stuff is such an over-exaggeration.
RIP GOOGLE VIDEO PLAYER Time of death 2007, we hardly knew ye!!
I can think of one noteworthy product that Google killed inexplicably, and it's Google Reader, their RSS reader. It's only partly inexplicable too because RSS feeds dramatically dropped in popularity from when Google bought/introduced Reader to when they end-of-lifed it. That's the only prominent product I can think of that they totally killed with no other features, app, or service to take over. Maybe Google+ too, but nobody misses Google+. Otherwise... Picasa? Photos. Panoramio? Maps. Google Notifier? Native notifications. Android @ Home? Google Home. Google Fastflip? Google Currents. Google Currents? Newsstand. Newstand? Google News. Grandcentral? Google Voice. Writely? Google Docs. etc
This thread is a great example. "Google killed Google trips!! On no what am I going to do?!!" ... no they just rebranded it Google Travel (http://www.google.com/travel), and all of the info from Google Trips was always bubbled up in Gmail, Google Assistant, Maps, and all of their other products.
So many others on this "Google Graveyard" site aren't even dead, they're just features brought into other applications. Like, "Google Now" is on this list. I think *all* Google Now's features are built into Google Assistant and, on Android, the Google Search bar... it's just not a discrete app anymore. Same with "Google Glasses" (not the physical glasses, another product with photo machine learning). That tech was just rolled into Google Lens which is now just a part of the camera app on Android. Google Click-to-Call, it's just ... a feature in search now, not a separate product. "Google Real Time Search." It's just... built into Google search.
Oh no! GOogle Killed the Chromebook Pixel in 2017!!! ....... only to ... release the Google Pixelbook in 2018. It's like saying "omg I can't believe Microsoft killed the Xbox in 2004!" ... And then released the Xbox 360 and KILLED IT in 2014, and then released the Xbox One, which I bet they'll KILL in 2021!!
There's a ton that are very niche small open source programs that some developer published and stopped working on. Then there are a ton of things that nobody uses anymore or got replaced because of another product. OMG ... Google killed Google Toolbar for Firefox, Google Browser Sync, Send to Phone ALL IN THE SAME YEAR... HOW!? WHY!? Omg the victims! Oh... that's when Google Chrome came out...
Meanwhile Google's central paid products have persisted. Google Drive is one of the first products Google introduced payment tiers for, and it's still around 7 years later with no indication of slowing down. Google Play Store, despite many rebrands, is still the same thing with the same support for any app you bought ~10 years ago. Photos, YouTube Red/Premium, etc.
Well then, that shows my ignorance on the subject! I guess my question now is what does Google consider sucessful enough to consider supporting? If the API for Google's VR was that popular, what does a Google property have to do to maintain long-term support?When daydream was released, google had the most widely support, widely adopted VR API in the entire industry, with support that dwarfed the PSVR, Oculus Rift, and HTC Vive/SteamVR all combined.
I'm pretty sure I remember that very thread, too! It's just irritating and drive-by when someone just comes by, drops the link and hops out like they are somehow a free thinker.The Albatross did that and did it very well four months ago.
I keep quoting this in different Stadia threads because it's a great post, but very few people bother to read it, and fewer still bother to actually think about it. It must be more satisfying to dogpile with moronic "hurr durr this is DOA; this is Google+ all over again; something something Google Reader" posts.
1. This is Google, the company that kills most of their products.
The Albatross did that and did it very well four months ago.
I keep quoting this in different Stadia threads because it's a great post, but very few people bother to read it, and fewer still bother to actually think about it. It must be more satisfying to dogpile with moronic "hurr durr this is DOA; this is Google+ all over again; something something Google Reader" posts.
I understand what you're saying and I guess I don't disagree with that specific example, but there's a huge difference between Google killing something like Inbox or Reader, products that did not command a whole lot of time or money and certainly did not require people to pay for them, and killing a service like Stadia where Google has spent YEARS building out the infrastructure at tremendous expense and requiring people to pay for it. I am not aware of any services Google has deprecated where users had spent money for content and then they lost that content as a result of the service being shuttered. That's the comparison people keep making and it doesn't hold up.This is all really, really poor handwaving of what that document is saying. Expressing that some vestigial technology remains in subsequent technology is technically correct, but completely immaterial to consumers and developers, considering that nearly everything listed is a service, aka SAS. It's absolutely, 100% correct to point out that the entire developer ecosystems reliant on those services were killed.
This is like saying "Sega didn't kill the Sega Master System, the Z80 and original VDP are still there in the sega genesis!" or "Nintendo didn't kill the Wii, the entire Wii is present in the WiiU!" or "Microsoft didn't kill the original Xbox nor the 360, the Xbox One can play those games!" Which is like, ok, sure, but the economic environment -- the domain where consumers and developers interact -- is dead and no longer supported. A subsequent technology replicating the function, while abandoning the service, is the exact same thing as killing the service.
I understand what you're saying and I guess I don't disagree with that specific example, but there's a huge difference between Google killing something like Inbox or Reader, products that did not command a whole lot of time or money and certainly did not require people to pay for them, and killing a service like Stadia where Google has spent YEARS building out the infrastructure at tremendous expense and requiring people to pay for it. I am not aware of any services Google has deprecated where users had spent money for content and then they lost that content as a result of the service being shuttered. That's the comparison people keep making and it doesn't hold up.
Fair enough. We will probably have to agree to disagree about this element insofar as Stadia as concerned, because it seems like all the posts about how Google kills services so frequently is couched in the fear that people are going to buy games and then just lose them if Google shuts it down. My posts have been an attempt to try to assuage those fears, I guess. I understand there are other impacts of those kinds of services being shut down, but it doesn't really pertain to the fear of losing content an end user has paid for."I didn't spend money on this, so it doesn't count that it doesn't exist" is some silly justification. For one, developers on such projects oftenlose their jobs so there has always been a financial element. Further, it's proof that just because Google puts money into a project, doesn't mean they are committed to it.
But really, that post is nothing more than "This project that they explicitly financially supported at one point, then stopped financially supporting, doesn't count when talking about a list of products they once supported then stopped, because I didn't lose money."
I understand there are other impacts of those kinds of services being shut down, but it doesn't really pertain to the fear of losing content an end user has paid for.
Not that I really agree with Fedrik, but to be fair Sony dropped Vita like a rock after 2013.I feel like you thought this post was smart.
But surely you see the difference between platforms not having support from third parties and not having support from the creators, right? One is Sony the other is Google.
I would love to see this thing deemed as a troll post in Stadia threads, because it is always, always take out of context and spreads a whole lot of FUD. Half of what's in there was rolled into something else and the rest was either closed because of lack of use or duplicated function (or rebranding). Nexus was not "killed" it was evolved into Pixel, for instance.
Reader is part of play and was rolled into that. At this point a lot of the old apps are part of either play or the general Google app.Even if say half of that list is out for the reasons you mentioned - it is still a huge amount of products killed off. I've certainly been attached to Google products in the past that have unceremoniously received the axe (Google Reader anyone else?). They are, as a company, notoriously averse to long term approaches. If it isn't an instant success, they seem to want nothing to do with it.
I think that information is vital to Stadia, to be perfectly honest. It's a risk you take with any product really, but *especially* from Google.
This is like, one of the most direct comparisons you can make though. Daydream was a platform with paid apps. Apps which will now be unusable on new hardware going forward.This forum needs an official "Stadia shitposting" thread. The amount of discussion about it in unrelated threads is nuts.
Except for the part where Stadia's input lag would've made VR unplayable.Stadia would been a PERFECT MATCH for Stadia. Imagine full blown VR games streaming to your phone. No wires, no PC.
Unless they're planning to revamp Daydream entirely, this was a bad move.
How's that other big Google AR investment going? Magic Leap I think it's called.
Phone VR is dead with standalone headsets like Oculus Go and Quest having arrived. Having a fixed & dedicated headset provides many technical advantages despite the BOM being about the same or less compared to a phone + VR add-on.
Well then, that shows my ignorance on the subject! I guess my question now is what does Google consider sucessful enough to consider supporting? If the API for Google's VR was that popular, what does a Google property have to do to maintain long-term support?
I don't know why they spent so much R&D on this project and not actively promote or support it (outside of that one big conference)
I had to do the googles.....I thought it was an old program or something it was launched in 2016. Sony let SOCOM servers run longer than thatKilling a platform, no matter how dead it was, right before launching another kinda-related platform, is a hilariously bad move