• 3 years ago
Flowplayer “Native” (v1.0)
In 2016, we set out to build a player that shakes the common understanding of online video.
3 minutes read
By building the player from scratch we were able to reduce the complexity to one-tenth of a traditional player. This lead to increased stability, because now we have ten times less room for errors.
Flowplayer "Native" is a complete rewrite of our player.
First, easy decision was to drop Flash and use the native video API for everything. As developers, we prefer to work with the standards and avoid “vendor lock-ins”. Because learning standards make us better developers and make our code safe from the changing future.
By building the player from scratch we could reduce the complexity to one-tenth of a traditional player. This lead to increased stability because now we have ten times less room for errors.
We also realized down the line that native video allows us to do new kinds of innovations such as starting the playback right away without loading any of the player code. We just progressively enhance the video tag once the Flowplayer components start appearing from the network.
Nothing is faster than that.
Flowplayer is the most deployed player on the Internet, right after YouTube and Vimeo. We know a few things what people want.
People want this from design:
Other than that, we must stay away and use as little design as possible. Obey the 10th law from Dieter Rams.
Flowplayer Native is our latest wrapping of this knowledge.
Since we had this goal of building an insanely small player, we knew where this would lead us: doing the SVG graphics "by hand".
It felt like working with a low-level assembly language or finding the right character slots in an ASCII art.
We are happy to serve several of the largest media companies in the world and learning from their needs.
Typically they just want to maximize their ad revenue.
So we decided to build the most revenue generating player out there.
After studying the subject we came to a naive conclusion: the preroll ad is the biggest revenue bottleneck. It's not only the most popular ad format but also the slowest. So in order to help our customers with their mission, we needed to load preroll ads as quickly as possible.
We did everything that is possible in the current state of the VAST-dominated industry: minimize DNS lookups, use HTTP2, optimize CDNs, load the ad as early as possible, figure out how various ad servers work, and use pre-fetching wherever possible.
And then find the perfect balance between different browsers and customer environments with an endless amount of trials and errors.
It's hard work and not always that much fun.
We now have that balance and the ads load very fast. You can explore your improved analytics here.
Finally, let's get into details about the supported browsers.
Obviously, we don't list every possible browser and version, because that would take hundreds of viewports of screen real estate. Some rows are bluntly listed as We don't know because we are mostly reliant on the options available on the fantastic BrowserStack service and iOS simulator.
50k plays/mo included
150k plays/mo included
All Standard freatures
Min. 500,000 plays/mo
Android and iOS SDK