AMP it up | Flowplayer

In the AMP ecosystem, it's possible to define custom components, but we as the Player Team made the conscious decision to not do that, much to the dismay of our marketing team.

Instead, we opted to build our very own AMP integration using the common amp-iframe-video component, which is a core component managed directly by Google's AMP team.

Why did we do this?

Less code equals fewer bugs. The amp-iframe-video component is already one of the most reviewed, battle-hardened pieces of code in the amp project. To throw that value away from our partners that want to use AMP by rolling out our own component seemed like an exercise of vanity.
By using a well-known, well-documented component we require less vendor-specific knowledge to acquire. This also fits well with the Native paradigm, where we build as much as possible on top the raw HTMLVideoElement without requiring special knowledge, the Web's power is in integrations, not silos.
The third reason was performance-related. We wanted to keep our already fast response times as low as possible. By using something that already exists, it allows us to focus on building out what our part of the integration does, without needing to go through the process of external reviews. This means that when features are requested, it should make it quicker for us to implement them.

If you have any questions or if you are interested in learning more about Flowplayer//AMP, please feel free to reach out to sales.