Chromecast Over the Top SDK Integration

Chromecast works by ‘casting’ content from an external source to a screen, such as a TV. For this reason, SDK support is not tied to Chromecast, but rather is based on existing SDK integration with the source content being cast. In other words, Chromecast is not a platform with standalone SDK support, but is rather a means for displaying existing content on another screen.

The following example scenarios describe how the SDK is integrated in relation to Chromecast:

 

Casting from a Mobile App:

If content were cast to the TV from an iOS or Android mobile app on a smartphone, the mobile app itself is responsible for measurement signal, and thus would be utilizing our iOS or Android SDK accordingly.

 

Casting from Web:

If content were cast from a web-based source, that web-based source would utilize our Web SDK for measurement signal.

 

Casting from Web via the Mobile App:

A mobile app may often be cast to the TV while sourcing its content internally from the web. In this case, the measurement signal would originate from the mobile app using our iOS or Android SDK, while additional measurement signal might also be generated from the web-based content source using our Web SDK, although this content would still be passing through the mobile app. An identity link or other mechanism could be used to tie these two sources together, but this is a discussion that should be had with your client success manager as there is no one-size-fits-all approach to this scenario, and it largely depends on your needs and expectations.

 

Chromecast with Google TV:

Chromecast with Google TV is unrelated to Chromecast. Apps targeting “Chromecast with Google TV” would integrate our Android SDK.