How to harness and iterate on viewer data across multiple platforms
In part one of our series on Architecting a Front-End Stack for Multi-Screen, we looked at different cross-platform frameworks and how portable they are when stretching user experiences across mobile, tablet, and TV.
Part two looks at the question which comes after. Now that you have your streaming video app on multiple platforms, how do you harness all the data coming your way?
The streaming video experiences of tomorrow will be built on top of intelligence and capable of delivering the right experience, to the right user, at the right time. This will be possible thanks to viewer data coming from a number of platforms at once. So, companies won’t be monitoring data on a device basis but rather, a profile basis.
This means that personalization will be more important than ever before. Scalable OTT apps need to be able to support the conditional roll-out of experiences based on user context. These experiences need to have the ability to be updated on-the-fly without impacting the quality of the user experience being delivered.
Among the frameworks we looked at in my previous entry, a cross-platform Engine proved to be the most portable while maintaining a high-performing UX. With an Engine approach, multi-screen experiences can be instrumented to support the collection of data across every platform.
With an Engine, an architecture can be put in place that leverages a combination of natively executed code and dynamically retrieved scripting.
To view a detailed breakdown of the above chart, including more information when developing for cross-platform, download our latest whitepaper.
With this paper, you will be able to make an informed decision on how to best manage your cross-platform OTT strategy and streamline your development process. Download Architecting a Front-End Stack for Multi-Screen, written by You.i TV CTO, Andrew Emmons.