Today, we are thrilled to announce the full support of every device, OS, platform and programming language for Strive’s P2P Video Delivery technology Flink. Together with our new technology partner Pion WebRTC, we managed to combine Pion’s native WebRTC stack with Strive’s unique P2P video delivery software to a single software library, based 100% on the programming language Golang. Thanks to Golang’s incredible platform compatibility, every combination of device and operating system is now WebRTC ready!
OPTIMIZE YOUR OTT VIDEO DELIVERY ON ALL DEVICES AND APPS
Integrate Strive’s P2P Video Delivery SDK Into Your Web Application, iOS App, Android App, Set-Top Box or Smart TV. One SDK For Every Platform, OS And Language.
FULL SUPPORT, THANKS TO OUR NEW TECHNOLOGY PARTNER PIONS WEBRTC
In order to make Flink OTT accessible for all devices and platform, one of our main goals right from the start was to have one codebase that could be re-used for all different scenarios and use cases. This was a very difficult challenge, as WebRTC – the main driver behind Flink OTT – was only supported by web browsers. To achieve our goal, we would have to re-implement the entire WebRTC protocol in a programming language that would allow us to create native libraries for every OS, CPU architecture and programming language. We knew that one day we would have to do this but focused on all other tasks besides the portation of WebRTC.
HOW WE TRIED TO AVOID IT
As the WebRTC topic was our biggest challenge, we tried to set up everything else that would have to be done in order to provide a native Flink OTT SDK library. So we came up with the idea to design our P2P video delivery client as a local proxy-server, that a web player can connect to when requesting video data. A developer would just have to “modify” a manifest URL for a given video stream and pass it into our SDK. The SDK would then return a new URL that points to the locally running proxy server. Whenever video data is requested from this server, it first applies the Flink OTT logic to it in order to fetch data from Strive’s P2P network. All remaining call would just be passed to the original content URL.
HOW WE (OR ACTUALLY SOMEONE ELSE) SOLVED IT
As we finally had everything set up and finished the development of all parts except for the WebRTC stuff, we thought “well, ok this is going to be the hardest part”. But as we quickly found out, we were not the only ones with the idea of bringing WebRTC to native languages. It turned out there was an ongoing project called Pion with the exact same goal! Just when we thought, things could not get better, we saw that Pion was written in Golang, the language on which Strive’s entire codebase is built upon!
We contacted Pion to ask for a PoC and they happily accepted. Just a couple of weeks later, we were done. Flink OTT was fully powered by Pion’s WebRTC library and was ready for the launch!
DO YOU WANT TO SEE IT IN ACTION?
Currently, we are building a lot of bindings for example an iOS XCode Project, an Android Studio, a Python library and much more wrappers and libraries. But what we would really like to know is which bindings you require the most. So if you want to see Flink OTT Native in action, just contact us and we will prepare a dedicated showcase for your use case.