Overview

this chapter focuses on providing an overview of the concepts and the architecture of the nativewaves exp framework framework approach and extensibility with nativewaves exp we have adopted a framework approach that enables integration with existing partners and other technologies we understand the importance of respecting the technology choices and existing partnerships of broadcasters and streaming platforms our objective is not to replace current systems with a white label product, but rather to take existing experiences to the next level by doing so, we target concerns regarding the technical complexities associated with creating next level watching experiences and make this process easy our products provide seamless integration capabilities for various elements such as custom content resolution, metrics and user analytics, and custom media players when it comes to the final front end integration, we provide two options to our customers the first option is to utilize pre built user experiences developed by nativewaves for different event and sport types these experiences can be further customized and themed according to preferences the second option is to build a custom user experience using the nativewaves exp engine as a technical foundation the exp framework the nativewaves exp framework consists of multiple parts, visualized in the diagram below exp engine exp manifest exp appconfig exp selectors + exp handler exp watching experiences exp components overview exp engine the exp engine is the heart of the exp framework it has the following responsibilities responsible for one watching experience needs to be independent of ui (can work with any ui by connecting to pre defined interfaces) needs to be framework independent (e g independent from react) can handle multiple exp manifests (e g for conference experience) enables communication between different experiences (common communication interface) at the moment, the exp engine is primarily a conceptual element and will mostly align with the exp core sdks that are described in the later section for the web, android and ios sdks please find more information can be found in the exp engine docid yuy66m8av4of6qfsqaa section exp manifest the exp manifest serves as a repository of relevant information for the event watching experience it focuses on time information, av (audio/video) playback, and specific details related to an event more information can be found in the exp manifest docid\ rlfte lps44hdjfyopv2l section exp appconfig the exp appconfig enables remote configuration and control of pre built nativewaves experiences it handles theming, customization options, and more, providing a centralized platform for easy management more information can be found in the exp app config docid\ xp7flcqooltm5vpicwvzh section exp selectors & exp handlers an exp selector is the part of the app that selects and chooses which experience should be loaded this can be done using the selection logic from the exp app config docid\ xp7flcqooltm5vpicwvzh or by implementing your custom decision logic inside your app the exp handler is the part of your app that manages an instance of an event watching experience exp watching experiences the exp watching experience is the actual part where the playback, playback controls, data integration, etc is rendered and visualised