![]() While integrating FireStick, you have two options for displaying content on the receiver device: handling every cast receiving device differently could be error-prone and would require maintaining a much bigger codebase.It needs just little adjustments, as FireStick from outside is handled exactly in the same way as Chromecast having Google Cast already integrated, it is much easier to add FireStick as a cast framework's external provider, because there is no need to rewrite existing code.MediaRouter manages cast devices picker dialog and cast button state. lots of UI-related tasks are handled automatically.Great cooperation of Google's cast framework and MediaRouter handles a lot of things out of the box: We also needed a way to manage routing events and communicate with the receiver. Handle all FireStick session management by hand, not using Google's Cast Framework.īecause we had already been using Google's Cast Framework and concluded that it would make integration much easier, we decided to use option number 1.What is great, it lets you define other cast receiver devices, apart from Chromecast. A very important thing to mention is that in order to add Google Cast to your app, you need to use Cast Framework for Android. While planning integration, we had 2 options to choose from: Below, you will find how we handled it, and the most important lessons we have learned. ![]() There was a story point in it, in which we had already integrated Google's Chromecast in our app, but got lots of requests to integrate Amazon’s FireStick. This also refers to the project I am working on. One of the most important features of media apps on the market is the possibility of casting their content. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |