Skip to main content

Quick and dirty Android YouTube fullscreen sample code.

I am currently developing an application that requires playing YouTube videos in full screen mode. After scraping around and putting together the pieces, I currently have the following code which I hope is of use to anybody else out there.


  public void playYouTubeVideo(String videoId) {

    String videoTemplate = "@YTBASE@@VIDEO@";

    String videoAction = videoTemplate
        .replace("@YTBASE@", "vnd.youtube://")
        .replace("@VIDEO@", videoId);

    Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(videoAction));
    intent.putExtra("VIDEO_ID", videoAction);
    intent.putExtra("force_fullscreen", true);

    startActivity(intent);
  }

There are some points to bear in mind though...
  1. Once the ACTION_VIEW intent has control, your application is effectively paused i.e. it won't work until you use the back button to exit the player intent and return to your application.
  2. It may or may not work in the future of YT change the way they operate, but that's always the case.
Point 2 is the reason I have used the variables videoTemplate and the @ delimited markers... hopefully you can see what's going on there and change it in the future if you need to.

I now realise that I may well have to use the "official" YouTube API and create an application API key and all the rest of it but if it means seamless integration then I will do just that but I thought I'd at least share what I had so far.

So, I hope the above serves useful to you. Back to the hack...


Labels:

Comments

Post a Comment

Popular posts from this blog

Communicating between controllers in AngularJS

I have seen many solutions to how to make controllers talk to each other whilst at the same time remaining within "da rulez" of writing Angular applications. I have been using Angular for about a month now and at times it has been swearier than a good Haskell session, it is most definitely worth it all in the end. I have written a really nice looking web application for my employer and they seem to like it. I think Angular. One thing I really aced (to my own satisfaction at least) was wrapping a REST (of any type) API using a resource. I will make a separate post about that. Do the simplest thing... Here is my own solution to the problem of how you can make different controllers communicate cleanly using the "event" system that Angular provides. All you have to do is ensure that the following event listener is added to your application root-scope: App.run( function( $rootScope )) { $rootScope.$on('broadcast', function( e, data ) { if (undef...
3 comments
Read more

Cross platform development with Scheme

Just a quick note about something I recently found whilst trying not to buy MOCL… http://www.lambdanative.org/ LambdaNative is developed and maintained by the Pediatric Anethesia Research Team (PART) and the Electical and Computer Engineering in Medicine (ECEM) group at the University of British Columbia (UBC). I have spent a week or two evaluating it and accidentally contributed a pull request that got merged and one that didn’t and I have to say that, for what it offers, it is awesomely good. Having personally spent many hours with it now, I do not yet think it is ready for mainstream development for a few reasons. I don’t mean that it a bad way either. What I mean is that the language, Scheme, is not really that widely known and as such it probably won’t break out into the public arena any time yet. That’s a real shame because I think that they have achieved an amazing thing; total abstraction of the underlying platform with a really powerful, underestimated language. ...
1 comment
Read more

Handling multipart/form-data with NanoHTTPD

I am in the process of reviving an old project from 2014 that I never finished because of other work commitments. In that time, bitrot has set in, the Android API has moved on and all in all, the home-brewed HTTP server I wrote using SocketServer and the org.apache libraries had to go! I looked around, found a couple of contenders and after much time decided to go with NanoHTTPD because it is lean, small and fits in exactly two files. The main server is in one file `NanoHTTPD.java`and there is another file called `ServerRunner.java` which manages instances of running servers. The others The other project I looked at is this one:  https://github.com/koush/AndroidAsync which led me a merry dance and I just couldn't figure out how get the POST data I had uploaded. I spent a few days really digging at it with Wire Shark too to make sure the data was going up. It was. Whatever... I had used it via a gradle dependency entry but I dropped it and went back to NanoHTTPD. For m...
Post a Comment
Read more