Google Cast is an emerging technology that enables a multi-screen experience to users. It is a screen-sharing technology that allows users to send and control content from their computing devices such as laptops, tablets and smartphones to their TVs screens.<\/p>\n
In this blog, we will take you through few steps to begin with the Cast session. The important point to remember is that when you are about to begin the Cast session, both the sender\u2019s and receiver\u2019s devices should be connected to the same WiFi.<\/p>\n
There are two ways users can start a Cast session:<\/span> Few Requirements:<\/span> Developing Sender App:<\/span> <\/p>\n 2.<\/strong> Create empty Android application and add the following libraries as dependencies:<\/p>\n [java]android-sdk\\extras\\android\\support\\v7\\appcompat 3.<\/strong> meta-data element is required in Manifest:<\/p>\n [java]<meta-data 4.<\/strong> Application\u2019s theme:<\/p>\n [java]android:theme="@style\/Theme.AppCompat"[\/java]<\/p>\n 5.<\/strong> Adding the Cast Button:<\/p>\n [xml]<menu xmlns:android="http:\/\/schemas.android.com\/apk\/res\/android" Developing Receiver App:<\/span> Functions of Receiver Application:<\/span> Types of Receiver Application:<\/span> 2.<\/strong> Styled Media Receiver:<\/strong> 3.<\/strong> Default Media Receiver:<\/strong> Default Media Reciever ID:<\/span> Technical Details:<\/span> Limitations:<\/span> Hope this was useful to the readers.<\/p>\n Happy Casting !!!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" Google Cast is an emerging technology that enables a multi-screen experience to users. It is a screen-sharing technology that allows users to send and control content from their computing devices such as laptops, tablets and smartphones to their TVs screens. In this blog, we will take you through few steps to begin with the Cast […]<\/p>\n","protected":false},"author":167,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2},"categories":[518],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/18011"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/167"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=18011"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/18011\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=18011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=18011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=18011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n1. Connect & Play:<\/strong> As the name suggests, one needs to connect to the Cast receiver first before playing the content.
\n2.<\/strong> Play & Connect:<\/strong> In this the content gets played first and the user connects to the Cast receiver later.<\/p>\n
\n1.<\/strong> Minimum Android SDK version that the Cast SDK supports is 9 (GingerBread)
\n2.<\/strong> Cast application development involves development of Sender and Receiver applications.
\n3.<\/strong> Package require: com.google.android.gms.cast
\n4.<\/strong> You need to register your application in order to get application ID (which will be used in both \u201csender\u201d and \u201creceiver\u201d applications).
\n5.<\/strong> Register your Google Cast device so that it may access your receiver application before you publish it.
\n6.<\/strong> It can take up to 6 hours to publish your receiver app.<\/p>\n
\n1.<\/strong> Classes used:<\/p>\n\n
\nandroid-sdk\\extras\\android\\support\\v7\\mediarouter
\nandroid-sdk\\extras\\google\\google_play_services\\libproject\\google-play-services_lib[\/java]<\/p>\n
\nandroid:name="com.google.android.gms.version"
\nandroid:value="@integer\/google_play_services_version" \/>[\/java]<\/p>\n
\nxmlns:app="http:\/\/schemas.android.com\/apk\/res-auto" >
\n<item\u00a0\u00a0\u00a0 android:id="@+id\/media_route_menu_item"
\nandroid:title="@string\/media_route_menu_title"
\napp:actionProviderClass="android.support.v7.app.MediaRouteActionProvider"
\napp:showAsAction="always"\/>
\n<\/menu>[\/xml]<\/p>\n
\nChromecast is the device which can run the special form of Web Application called \u201cReceiver\u201d<\/p>\n
\n1.<\/strong> An interface to display the app’s content is provided.
\n2.<\/strong> To control the content (messages) on the receiver device from the sender application.
\n3.<\/strong> It handles custom messages from the sender application that are application-specific<\/p>\n
\n1.<\/strong> Custom Receiver:<\/strong>
\nThe content such as an image gallery or game the app would require DRM, or requires support for media types. You host an HTML 5 app on your servers using the JavaScript Receiver API.<\/p>\n
\nGoogle hosted a Pre-built receiver application which is designed for streaming audio and\u00a0\u00a0 video content.<\/p>\n
\nYou don\u2019t have to register with the Google Cast SDK Developer Console, and you cannot customise any of the UI.<\/p>\n
\nCastMediaControlIntent.DEFAULT_MEDIA_RECEIVER_APPLICATION_ID<\/p>\n
\n1.<\/strong> Same WiFi network is to be used for both sender and receiver device.
\n2.<\/strong> Media Player Library supported types: PlayReady, Widevine.
\n3.<\/strong> Optimized android apps: Youtube, Netflix, Google Music, Google Movies.
\n4.<\/strong> Audio formats that support are MP3, Vorbis, Wav.
\n5.<\/strong> Streaming protocols: MP4, WebM are validated.
\n6.<\/strong> Image formats that support are BMP, GIF, JPEG, PNG, WEBP.
\n7.<\/strong> Download the Google Cast Extension for Crome browser.<\/p>\n
\n1.<\/strong> Cast Device is with memory, CPU and GPU limitations and it is also a low-power device so the receiver application.
\n2.<\/strong> In Receiver app we cannot create Tabs, windows or popups, and there should be nothing on the receiver device screen requiring input. All the interaction is to be done through a sender application.
\n3.<\/strong> Only one video will be active at a time.
\n4.<\/strong> Video compositing, manipulation, transformations, rotations or zooming are not supported.<\/p>\n