The first step: the sender app uses SDK, Send the media content that needs to be screened to Google’s server, Receive notification from Google server
Step 2: Play (all senders and receivers must be able to access Google servers). The receiving end is running a browser, which will load a corresponding web page according to the app ID and media information of the sending end. This webpage is provided by the developer of the sending 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 also be loaded and rendered.
The difference between Google Cast and Apple’s AirPlay or DLNA
One is to rely on Google’s server, 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. Google Cast needs to provide its own receiver app. The advantage of this is that developers can be highly customized ( For example, you can customize the UI, or add complex functions such as barrage, scrolling lyrics, and music visualization), Although the receiver is often not running an open operating system like Android, But because the essence of the receiving app is a web page, it is not difficult to develop.
The difference between 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, 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 Google Cast’s mechanism.
The characteristic of this implementation is that the chromeCast dongle on the receiving end is provided by Google itself, and the developer’s burden is the application development of the sending end platform. Of course, the flexibility of the sending end 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. Provides the flexibility to use Google Cast API for development (of course, this can also be considered the limitation of the technology cannot support all apps)
Awind Inc. is a company focusing on wireless presentation systems for over 20 years, specializing in providing wireless presentation systems, screen mirroring, and wireless sharing software. The system can be applied on cell phones, tablets, and computers. We provide professional system integration wireless sharing solutions for future classrooms, flipped classrooms, multi-screen interaction, interactive teaching, network video, intelligent conference systems, multi-functional meeting rooms, etc.