Google Abandons Their Google Hangouts API (techcrunch.com)
"Once again we're seeing the hazards of developing using a third party service API," writes Slashdot reader BarbaraHudson, reporting that Google "will be discontinuing support for the Google Hangouts API going forward... Google Hangouts is now so insignificant that the cancellation didn't even rate an official blog post. As reported by TechCrunch, "just an updated FAQ and email notification to developers active on the API, forwarded to us by one of these devs."
TechCrunch writes:
As Google pushes Duo as its consumer video chat app and relegates Hangouts to the enterprise, it's dropping the flexibility to build these kinds of experiences. The email explains... "We understand this will impact developers who have invested in our platform. We have carefully considered this change and believe that it allows us to give our users a more targeted Hangouts desktop video experience going forward."
TechCrunch calls the move "a casualty of Google's fragmented messaging app strategy and the neglect of Hangouts itself." While some apps will continue working -- for example, integration with Slack -- their API's FAQ now ends with a reminder that "Users of apps will see a notice in the call letting them know that the app they're using will no longer work after April 25th."
TechCrunch calls the move "a casualty of Google's fragmented messaging app strategy and the neglect of Hangouts itself." While some apps will continue working -- for example, integration with Slack -- their API's FAQ now ends with a reminder that "Users of apps will see a notice in the call letting them know that the app they're using will no longer work after April 25th."
These are the hazards of relying on Google for anything. They throw stuff away constantly.
These days it's hard to write anything non-trivial without relying on something that will be hard to replace if it goes away, that's just a reality of modern software design. You can minimize the risk with abstraction and try to rely on open standards with multiple implementations, but at some point you have to just accept the occasional puzzle piece change as part of the business and move on.
That said, google pulls this shit all the time. Using a google API or service for anything critical would imo be a huge risk given their long history of suddenly killing things.
As a former Google employee, I can only laugh at this.
Throw one more on the pile. There's literally thousands more where it came from.
That company is absolutely infested with self-important assholes who all think they're the next big SV hot shit. Nobody wants to maintain anything and no documentation is kept up, because the brilliant geniuses hired out of college to make it all moved up or out three months later after shitting their half-assed garbage out in a flurry of sick buzzwords so impressive that nobody wanted to admit they didn't know what the fuck was being said.
Why is this still complex for people after 15+ years? Google's business is selling ads to an audience made captive by "free" email and search (I include Maps here) paid for by the privacy of that audience. The rest of what they do is wanking because they have more money than they know what to do with, the incremental info they get from most of these projects is nil. Google "strategy" these days is to make an inferior copy of other people's ideas, try to leverage their captive audience by strong-arming them and then failing anyway. People have been ripping on Apple lately, but Google is in exactly the same "no-innovation" spiral. They are ripe for disruption, it is only a matter of time.
Or maybe Google is closing something that is used so little that most developers who have put time and effort into it have written it off as a failure long ago.