Search This Blog

Sunday, December 10, 2017

The Feud Between Amazon and Google is Not Healthy

Is Amazon and Google really in an hostile relationship? If you are up-to-date with tech news, then you will know the right answer. For those who still could not figure out that there exit a feud between Amazon and Google I will explain it to you.

Back in 2015, Amazon outrightly ban the sale of Google Chromecast device on their site (, and this also including them deleting all the listing of the Chromecast device by third-party vendors. The reason:
Over the last three years, Prime Video has become an important part of Prime. It’s important that the streaming media players we sell interact well with Prime Video in order to avoid customer confusion.
In other words, Prime Video cannot be viewed by Google's Chromecast users. Is this Google's fault for not supporting Prime Video on Chromecast? No.
It is Amazon that chose not to put Prime Video on the Chromecast, and thus they are using that fact for banning the sales of Google Chromecast from their site.

Google is not retaliating by removing support for YouTube from Amazon's streaming devices come 2018. The frank reason for this move is:
We’ve been trying to reach agreement with Amazon to give consumers access to each other’s products and services. But Amazon doesn’t carry Google products like Chromecast and Google Home, doesn’t make Prime Video available for Google Cast users, and last month stopped selling some of [Google-owned] Nest’s latest products. Given this lack of reciprocity, we are no longer supporting YouTube on Echo Show and FireTV.
In other words, Google is saying that they’re willing to hold Fire TV and Echo Show users hostage in order to force Amazon to sell Google hardware on and also to make Amazon Prime Video to work on Chromecast.

If you are not a tech person, you might just laugh of this, but this isn't funny. This feud between Amazon and Google won't be making life easier for their customers. It is not healthy.

What do you think?

Also Read:
Team +Pinfoltd 


1 comment:

Search This Blog