Multiple Platform Integration

different platforms, screen sizes, and interaction capabilities (touch, mouse, remote) have a big impact on what the event watching experience can look like on this page, we explore different options and also look at synergies and experiences across multiple devices how users watch there is a range of multiple devices an event can be watched from in addition the user might also choose to watch on multiple devices at the same time for example, watching tv while using the phone however, we can already restrict a few devices which are typically not used as second screen devices phone (can be used as second screen) touch screen allows for very natural interactions e g swiping through camera perspectives native android and ios support allows for performant experiences web support also given, but video performance is inferior as compared to native playback web iframe integration easily possible safari on ios restricts functionality in full screen and workarounds are necessary (no web media extensions) different orientations landscape large focus on video content, perfect for multiview use cases portrait focus on other content, e g match stats, community features usually combined with landscape, when video content is available can also work as standalone experience when video content is not important or in betting use cases works for use cases where content owner forbid addition of any overlays to the video feeds fold special case not widely available on the market, but allows special multiview cases and full 16x9 display while accessing other features like match stats currently no special nativewaves exp support and is treated like a conventional screen tablet (can be used as second screen) very similiar to phone, except screen size differs usually a tablet is higher and 16x9 content is displayed with black bars at the top and bottom this is relevant as side bar menus and overlays could be different for example the side bar color might be different if we can assume a black border as in the phone use case desktop web only support, but still performant because of more processing power allows very easy iframe integrations desktop ui might be more complicated as there might be more elements on the screen however, in fullscreen playback mode all features are supported usually no touch screen and the usual form of control is a mouse this impacts interaction and navigation structure of the experience television usually 16x9 without black borders the remote control affects the experience considerably because the focus change has to be visualized and the application behaves completely differently than with a mouse or touchscreen ar / vr nativewavex exp does not provide a ar/vr sdk yet, but please mailto\ support\@nativewaves com and we are happy to assist you leverage the core components of nativewavex exp in your ar/vr applications screen size examples