logo

Introduction

In this section you will learn everything about how THEOplayer works with Chromecast.

Table of Contents

Sender Applications vs Receiver Applications

When a viewer is streaming through a Chromecast device, they are actually casting content from a sender application (e.g. an Android application) to a receiver application. A sender application informs a physical Chromecast device which receiver application it should load through an application ID.

If you have implemented THEOplayer in your sender application, you can enable Chromecast. Furthermore, you can also specify the application ID in your sender application.

Casting approaches

By specifying the application ID, you implicitly connect it with a type of receiver application. The following three types of receiver applications are common:

Type Maintainer Info Benefits Disadvantages
Default THEOplayer Receiver Application THEOplayer This is the default receiver application THEOplayer SDKs will connect with. The app ID of this default THEOplayer receiver application is 1ADD53F3 and it is hosted on https://d3ojqkc95d8mrd.cloudfront.net/. You (i.e. the developer) do not need to do anything extra on the Chromecast receiver application side. You don't need to create a Chromecast receiver, you don't need to register it at, ... - it just works. You are limited w.r.t. customizing the UI and integrating custom logic.
Custom THEOplayer Receiver Application Developer + THEOplayer This is a custom receiver application you can build, and where you integrate the THEOplayer Chromecast SDK. You (i.e. the developer) can adjust the look and feel, and integrate custom logic. You need to create a Chromecast receiver, register it, maintain it, ...
Customer Receiver Application Developer This is a custom receiver application you can build, but without using the THEOplayer Chromecast SDK. The THEOplayer Chromecast Receiver SDK is not a dependency. You are responsible for building and maintaining the receiver application, and its connection with the various sender applications.

Whitelisting Receiver Applications

Streaming services and products often require you to whitelist domain names to allow playback. When viewers are casting content to a Chromecast receiver application, your Chromecast device will actually stream the content on a domain name. In other words: CORS and whitelisting/blacklisting policies do apply to Chromecast sessions. Ensure that you've whitelisted the domain name which hosts your Chromecast receiver application. (You can look up the domain name of your receiver application at https://cast.google.com/publish/#/overview.)

If you're using the Default THEOplayer Receiver Application you may whitelist https://d3ojqkc95d8mrd.cloudfront.net/.

github
Make sure to follow us on GitHub!
THEO-logo-white
twitter
facebook
linkedin
Copyright © 2020. All Rights Reserved.
Leuven
New York
Singapore
Barcelona