Delegates

Use delegates when your app needs to react to SDK events, such as content starting to load, the player opening or closing, or the Viewer interacting with buttons your app owns.

Delegates are optional. If you don't need to react to events, you can integrate player sources without them.

Common use cases

• Track when the player opens and closes
• Show or hide loading UI based on player readiness
• Handle custom actions, links, or buttons
• Trigger app navigation based on Viewer interactions

How delegates fit in

Delegates don't change what content the SDK loads. They're a communication layer between the SDK and your app.

For entry points that can use delegates, see Player sources. For the broader delivery path, see Content delivery.