Using the player SDK means interacting with the
This interface provides functions to control video playback, content, position and rendering.
It also collects important events and dispatches them to subscribers that were registered with the
We recommend listening at least to the error event:
We provide different implementations that can be used within your app depending on your needs, but all of them share the same API surface described below.
Note: if you use the default controls, the user will be able to control the player through the user interface, so there's no need to interact directly with most of these functions.
Playback is controlled through simple
All player implementations can play a single
Video object, a list of
Videos or a
As soon as the content is set through
set (regardless of the play flag), it starts being buffered
and prepared for playback.
At any given time, you can retrieve the content
duration, the current playback
position and the
bufferedPosition, which is the position of the last video frame
available for playback. Buffering will proceed efficiently as the content is played.
We also offer
seek* functions to change the current position.
We also offer a few extra options that can be used to configure the player:
Quality.HIGH. We recommend to leave this on automatic mode to improve the user experience.
loop: whether the video should be re-played once it ends.
mute: whether the audio is muted or not.