Given 2 video URLs, one to an ad and one to your content, you can just make 2 serial calls to showVideoScreen() in appDetailScreen.brs. The downside of that approach is that users will easily be able to skip the ads. That's where roVideoPlayer comes in handy as Patrick mentioned. It gives you the ability to customize interaction with the remote control, disable FF, etc. To see how it works, take a look at section 5.8 of the Component Reference and the "Custom Video Player" sample included with the 2.6 SDK