This project falls under the license as defined in https://github.com/THEOplayer/license-and-disclaimer.
The sample application outlined in this project demonstrates the creation of a Custom CAFv3 Web Receiver app with the ability to play-out content provided by a connected THEOplayer sender application.
Building a receiver app using the v3 Cast Application Framework (CAFv3) is considered to be preferable to using the v2 Cast SDK because it is more consistent with the new CAF sender APIs, and has, among other things, support for voice control with Google Assistant, built-in ads and better queueing. However, it currently does not support a user-provided player, so it is mandatory to use the integrated player, either Shaka or MPL. The example project shows how the receiver can interact with a THEOplayer sender application.
A Web Receiver application is an HTML5/JavaScript application that runs on the Web Receiver device, such as a Chromecast. It comes with a built-in media player that provides a seamless and easy playback experience. It also allows a customized player UI and provides the ability to intercept and override messages and methods to execute custom business logic.
The sender application runs on the device held by the user, and manages the user's interaction with the content. For sender applications, Google Cast supports app development for Android, iOS, and Cast-supported web platforms. The sender application will not be covered in this document. We refer to the THEOplayer sample repositories for the corresponding platforms:
- Android: https://github.com/THEOplayer/samples-android-sdk
- iOS: https://github.com/THEOplayer/samples-ios-sdk
- Web: https://github.com/THEOplayer/samples-html5-sdk
Read more about how THEOplayer works with Chromecast in the THEOplayer documentation.