In Shaka Player Embedded you have the resource loading, player and view functionalities implemented in a single class, ShakaPlayerView. This seems unnatural, as they are completely different responsibilities, and makes difficult to implement a clear separation between view and model in the app.
On iOS you have:
AVPlayerItem which represents the resource to be played,
AVPlayerLayer which represents the layer where the played content is rendered, and
AVPlayer which represents the player itself and provides control over the media being played
I don't know if such a separation is technically feasible in Shaka Player Embedded, but in case it is, could you please consider implementing at least the player and the view in separate classes?
In Shaka Player Embedded you have the resource loading, player and view functionalities implemented in a single class, ShakaPlayerView. This seems unnatural, as they are completely different responsibilities, and makes difficult to implement a clear separation between view and model in the app.
On iOS you have:
I don't know if such a separation is technically feasible in Shaka Player Embedded, but in case it is, could you please consider implementing at least the player and the view in separate classes?