Receivers (except for the Default Receiver) are registered using a distinct app Service’s Cast Senders may run on any supported platforms (Web, iOS, Android)Īnd interact with the corresponding Cast Receiver running on Web or Android. Note: The Cast protocol is platform-independent, so a particular site or

A Cast-enabled Android device, such as Android TV.

A Chromecast connected to a high-definition television or sound system.

Google Cast supports Sender app development forĬast-supported web platforms, such as Google Chrome.Ī Receiver app runs on a Cast-enabled device, examples of which include:

Instance, one Sender could start a session on a Receiver and another SenderĬould join the same session to control playback, load new content, or queue moreĬontent for later. The Cast SDK also supports multiple Senders connecting to a Cast session. Examples ofĬast-enabled Receiver devices include Chromecasts, smart televisions, smart Responsible for responding to Sender commands and for conveying streamingĬontent from an online streaming service to the Cast-enabled device. The term Receiver refers to an app running on a Cast-enabled device that is The media controls in the Chrome web browser function as a Sender, as does There are many kinds of Senders, including mobile apps and Google Chrome webĪpps, as well as virtual control surfaces on touch-enabled Google Home devices. A Sender initiates the Cast session and manages the user's The term Sender refers to an app that plays the role of controllerįor the Cast session. While controlling playback using the Sender. Sender, and play it on (or cast it to) another device known as the Receiver,

The Cast SDK allows a user to select streaming audio-visual content using a

Chromecast from google chrome app