#CHROMECAST APP ANDROID#
#CHROMECAST APP TV#

The given event contains data like the senderId and the message content. The message itself will be passed in the customEvent parameter. This listener will be triggered when the sender app will send a message in the channel. Even if the method name is addCustomMessageListener you can only set 1 listener per namespace.

Here, we create a custom listener for our namesapce, the first parameter is the channel, the second is the listener.

This is used to send data back to the senders apps. As you can see, you can use way more than one namespace.

Define the custom namespace we will use and that it communicates in JSON.

You can use the packagename/applicationId you provided for your app, it’s a common thing to set urn:x-cast:applicationId if there is a single channel. For the demo, we will use only one namespace. (A namespace is a sort of specific named channel).

In our app (sender and receiver), we will send/receive messages with a custom namespace.An object that will contains our options.It replaces the CastReceiverManager from the v2 It manages “the cast session, senders, sending custom messages, and global system events”. The main instance of the CAF receiver is the CastReceiverContext.It is important to understand that it does not read messages directly from your app (or your chrome tab) but from a website. We need to understand how the cast technology works. So how can we do that? First, How does it work? With that said, I would like to see more games, more apps, more things compatible with this old friend.

#CHROMECAST APP TV#

Hey, it’s meant to be used on a TV isn’t it? The first version of the SDK was made to cast whatever you want, but the last version is clearly made for media casting (music, video, photo). I mean, technically, you can share whatever you want on your TV screen! But, most of the time, apps are not compatible (or you don’t know they are).

More, they are providing a SDK to help us interact with it.īut since, IMHO, the technology behind the Chromecast has not been really used. The first Chromecast was released in 2013 in the US (and 2014 in France).įrom the very first time, Google has designed the cast technology to be open to third party apps. If you don’t know where you’ve come from, you don’t know where you’re going - Maya Angelou Back to 2013

#CHROMECAST APP ANDROID#

Make your Android app compatible with your ChromecastĮspecially if your app is not a media app.

Chromecast app