Google Cast and ChromeCast
Google Cast is similar to DLNA, AirPlayer, Miracast, which is a kind of projection technology. Awind WiCS-2100 series wireless sharing and collaboration products support both Google Cast and Chromecast.
The basic working principle of Google Cast:
The sender app uses the SDK to send the media content that needs to be screened to Google’s server, and the server informs the receiver
Play (so both the sender and receiver must be able to access the Google server). The receiving end is running a browser, which loads a corresponding webpage based on the app ID and media information of the sending end. This webpage is provided by the developer of the sending end app and is responsible for playing the corresponding media content. Even if the receiving end is hardware that can only play audio, such as Chromecast Audio, this web page will be loaded and rendered.
The difference between Google Cast and Apple’s AirPlay or DLNA is that it relies on Google’s servers, which means that it must be connected to the Internet to use it. If there is only a local area network, it will not work. The second is that the latter two receivers are provided by the receiver itself. Developers only need to provide the content to be played, but Google Cast needs to provide its own receiver app. The advantage is that developers can be highly customized (For example, you can customize the UI, or add complex functions such as barrage, lyrics scrolling, music visualization, etc.), although the receiving end is often not running an open operating system like Android, because the essence of the receiving end app is a web page, it is difficult to develop Not high.
Chromecast and Google Cast
From the official website of Google Cast, we can see that the role of Google Cast is to send the content of small screens (such as mobile phones, tablets, and notebooks) to large screen devices (Google TV, Chromecast) through wireless (WIFI) for playback. That is to say, it provides multi-screen interactive functions from small screen devices to large-screen devices. What Google Cast does is to provide SDKs based on different platforms that provide the function of spending for applications. These platforms have senders and receivers. The senders have IOS, Android, and Chrome browsers, and the receivers have google TV, Chromecast. Wait, it can be said that this set of solutions is relatively large and comprehensive (in terms of the platforms it covers).
Chromecast is actually a specific implementation of the Google Cast mechanism. The feature of this implementation is that the Chromecast dongle on the receiving end is provided by Google itself, and the developer’s burden is limited to the application development of the sending end platform. Of course, the flexibility of the sending end Sex is also limited to the Google Cast API provided by Google.
Summarizing the relationship between Google Cast and Chrome Cast, in fact, Google Cast provides a set of APIs for interconnection between devices, while Chromecast technology is a specific implementation of this set of APIs. The advantage of this implementation lies in application development. The author provides the flexibility of using Google Cast API for development (of course, this can also be considered as the limitation of the technology cannot support all apps).