Amazon issued a cranky statement this week, objecting to Google’s decision to pull YouTube from its Echo Show smart appliance. But Google says it was no surprise to Amazon, which had been violating its terms of service.
And yes, those with bitter memories of the YouTube saga on Windows phone should see some similarities here. What this is clearly about is Google hampering a competitor. Which, you know, is technically both fair and legal.
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
“As of this afternoon, Google has chosen to no longer make YouTube available on Echo Show, without explanation and without notification to customers,” an Amazon statement explains. “There is no technical reason for that decision, which is disappointing and hurts both of our customers.”
Well, Amazon is right on two counts here: Google didn’t notify customers, and there are no technical reasons why YouTube videos can’t play on the Echo Show.
But Amazon is also conveniently leaving out the real reasons that this happened. That Google had warned Amazon about them violating its terms of service. And that it was Amazon, not Google, that never warned customers.
“We’ve been in negotiations with Amazon for a long time, working towards an agreement that provides great experiences for customers on both platforms,” a Google statement retorts. “Amazon’s implementation of YouTube on the Echo Show violates our terms of service, creating a broken user experience. We hope to be able to reach an agreement and resolve these issues soon.”
Frankly, I believe this is the first step towards the abyss for the Echo platform, which has become too popular too fast for the companies—Google, Microsoft, and Apple—that, by all rights, should be the market leaders here. Amazon can complain all it wants, but limiting a competitor’s access to a popular service actually makes sense. So I’m curious to see if there is a resolution. And whether YouTube does return to the Echo Show.
After all, we all know what happened with Windows phone.
skane2600
<blockquote><a href="#183742"><em>In reply to MikeGalos:</em></a></blockquote><p>I think it was a bit more complicated than that. IMO the only valid complaint was that MS made deals with OEMs that offered discounts only if they exclusively loaded a MS OS. Thus if you wanted to get DR DOS, you had to buy it separately. </p><p><br></p><p>Ironically that was the only "abuse" that didn't get a very good remedy. Instead the major competitors who lobbied for anti-trust got the big rewards (at least in the short term). IMO the fuss over Netscape, IE bundling, and Java were just BS. </p><p><br></p><p>Netscape was essentially one-hit company that didn't have a second act and whose management was ready to cash in at the first sign of trouble. MS had to include a IE-less version of Windows in the EU that nobody had any interest in buying. Sun made only a minimal attempt to market Java to consumers (where were the AOL-like Java CDs?) and the lack of Java apps on Windows and the Mac made clear how insignificant it was on desktop systems.</p>
skane2600
<blockquote><a href="#183834"><em>In reply to MikeGalos:</em></a></blockquote><p>Since I haven't read the trial transcripts I'll have to defer to your research, however it seems improbable that a one paragraph summary can capture the essence of 7,000 pages of trial transcripts. How does the "influential" argument apply to Java and Netscape?</p>
skane2600
<blockquote><a href="#184008"><em>In reply to MikeGalos:</em></a></blockquote><p>Perhaps when you are making a statement about a single finding among multiple findings you should make it clear from the beginning. </p>
Stooks
<p>Does Amazon allow you to "Cast" their Amazon Prime vide on a Chromecast? There answer is NO. Tit for tat basically. </p>
Lateef Alabi-Oki
<p>They probably pulled a Microsoft and reverse-engineered YouTube streams to circumvent monetization from Ads instead of using the official public YouTube APIs.</p>