Experience Examples
NativeWaves EXP is an experience creation framework that can be utilized for multiple use cases. We also offer ready-to-go solutions with NativeWaves EXP for selected sports to reduce the time to market and provide an easy starting point for an integration. Here some of these use cases:
You can easily integrate a complete pre-built experience from NativeWaves, including playback controls, advanced data overlays, replays, camera switching menu and more into your platforms via an IFrame (Web) or via a simple integration SDK (Web, Android, iOS).
It supports single and multiple views and automatically adapts the menus and navigation to the available content depending on the exact features. We offer integrations e.g. with StatsPerform data out of the box and you don't have to design the user experience yourself.
This holistic solution approach allows for very fast integration times to try out these types of features with your user base without having to spend too much time involving internal product, design, and development teams. The constraint, however, is that the customization options are more limited than with a own custom experience that can be tailored to your needs (see Theming & Customization)
Here is an illustrative example of what the pre-built football experience powered by NativeWaves EXP looks like on a mobile device:
A basic multi-view experience can be integrated out-of-the box without data and overlays, independent of the event type. The app integration works similiar to the experience above and has the same advantages and disatvantages.
If you would like to use the default NativeWaves EXP multi-view experience with event data such as match statistics and instant replays for an event type that we do not currently support, please contact us to discuss a possible custom development project or for further assistance.
If you want to have full control over your user experience, including design, feature set, and other elements, you can use NativeWaves EXP as a technical foundation and leverage some of the UI libraries that have already been developed for different event types. This requires more effort than using the standard NativeWaves EXP experiences described above, but gives you complete control over how you want your event-watching experience to look within your app. You can use NativeWaves EXP components, including systems such as content scheduling, media orchestration, timeline handling, synchronization, data handling, and others, and integrate directly with your existing systems.
At the moment, we don't fully offer low-level access to all NativeWaves EXP components in our SDKs out of the box, but we can provide access to existing components and work with your developers to integrate more advanced concepts into your application. We do custom projects for this purpose and analyze your technical stack to provide you with the fastest integration route.
NativeWaves EXP can also enable you to deliver a synchronized second screen experience to your viewers. Using our patented sync solution, we use the broadcast audio to sync the mobile device to the TV. The mobile device listens to the TV audio for 5 secs and then syncs it to the TV. Take the example of a motorsport race. The idea is that you watch motorsport on your TV and then you take out your smartphone and sync it to the TV and suddenly you have access to all the cool additional content like onboard cameras of your favourite drivers, helicopter cam and other driver information. All the other additional features such as data and analytics, social media integration and instant replays can also be offered to the viewer on the second screen.
The main reason we need to synchronize with the TV is the difference in latency between the different broadcasting and streaming routes. For example, the lens-to-screen latency between what is happening on the race track and in the living room is between 3 and 10 seconds for linear TV depending if your are watching via cable, satellite or IP. If the same signal is streamed to a mobile device via traditional protocols over the internet, it can take over 30 seconds. We adress this by using low latency streaming to deliver the signals to the mobile device faster than the TV (under 3 second) and then synchronizing it with the current point in the TV signal by using the TV audio.
Here a short video that illustrates this process with a football example: