Overview

the fundamental principle of nativewaves exp revolves around the production of a manifest for an event or event session which we call the exp manifest docid\ rlfte lps44hdjfyopv2l when we speak of an event, we mean for example, a football game, a hockey game, a motor race or a muscial concert when we speak of an event session, this could refer to a qualifying session or the actual race session connected to a motorsport weekend, which could be treated as two separate events in our production nativewaves exp flow the exp manifest docid\ rlfte lps44hdjfyopv2l serves as a comprehensive description of an event, encompassing various aspects such as content streams, timing, metadata, and more once the manifest is generated, it is then passed to the nativewaves exp engine docid yuy66m8av4of6qfsqaa which is part of the nativewaves exp sdk ( introduction docid\ pn8yeterfwywpwnlrywe6 , introduction docid\ g8ckisp2veuyv4oujo030 , introduction docid\ m2e 3dwczzjk27ntapy2r ) and is integrated into a fronted application the smep service docid\ bahfu3fbshk0ctqauif9e , an integral component of the nativewaves cloud platform docid\ nvstigq7vuyrvila15qpw , takes charge of generating the exp manifest docid\ rlfte lps44hdjfyopv2l in the backend operating through the nativewaves console , the smep service facilitates the setup of events for real world occurrences within the console, all relevant information and content streams (video, audio, data) can be linked to the respective event in the background, the smep event system diligently analyzes all content streams and periodically updates the exp manifest this dynamic process ensures that any changes, such as event start or end times, are recognized and managed by the event system consequently, the exp manifest timeline and all associated content objects are automatically adjusted the following image illustrates this flow of content and data nativewaves exp flow step 1 content production and sending to nativewaves platform content is produced as part of event production the produced content is sent to the nativewaves platform this content can be streamed by either the nativewaves platform itself or an external system, as the platform supports external stream urls step 2 smep service & creation of exp manifest the smep service receives the content stream metadata information it also gathers any related event data such as match statistics and event information the smep service integrates and processes all this information the smep service generates the exp manifest the exp manifest contains all the necessary information for creating the user experience the exp manifest is then sent to the frontend application step 3 exp engine and user interface the exp engine processes the exp manifest received from the smep service together with the user interface and event logic, the exp engine generates the final experience the user is shown the finalized experience, combining the content streams, metadata, event data, and interactive elements next sections in the following sections we describe how to basic event setup docid\ yii348rxyhj6ssi n whm to simulate the above described process, and add it to a showcase collection that can then be watched in the nativewaves showcase app docid\ hqr84awi447cxktbh2g8o in order to work with the console, a account setup & console docid\ ca8cqchrxdhtkzrkdsorq needs to be setup and an environment needs to be created