I am trying to wrap my head around the overall usefulness of this R.A.F. and not having much luck so far. Can someone help me see the light?
So it parses the templating of VAST, i get that. But if i have the VAST ad server on hand and am not afraid of parsing XML, why would i want to use "RAF"? The argument that it will update itself with the rOS is kind of weak.
And i find it disturbing that the library BRS source is kept hidden from us. Using the library (content unknown) makes RokuCo a man-in-the-middle intermediary between publisher and advertiser. What do we know about the "privacy" of the exchanges? What of them will the Co collect/aggregate/peruse? - i don't see a statement on that.
As for the "man-in-the-middle" concern, I don't think that's any different than using the third party libraries for VAST on iOS and Android, which most ad services also provide. Some, like LiveRail, also provide a BrightScript library which you could use instead, if you were so inclined.
RAF is in release form. I'm not currently aware of ads being sold as skippable outside of the YouTube channel on Roku.
However, with the RAF capability for interactive ads (via Innovid and others) there is the capability to sell skippable ads moving forward.
I think the main issue I see with skippable ads is how to make them economically viable. YouTube has such a massive audience that they can make the economics work with users skipping ads en masse. But smaller publishers that don't have a billion unique users in which to cast such a wide net and make the numbers work. As the AVOD market continues to mature the ad diversity/frequency issue should resolve.
RAF.setAdExit(isEnabled as Boolean)I tested and - yes indeed! - if that's enabled, one can back off from RAF ads with the "Back" remote key - with RAF.showAds(adPods) call returning false to flag the interruption.