IPlayerClient instances in the UI layer communicate with VideoPlayer instances in a separate service layer via JavaScript Interface (JSI)-based inter-process communication (IPC). You’ll set up a dual-player architecture with a main player client for content and an ad player client that plays ads during ad breaks, either on a video surface shared with the main player or on its own dedicated surface.
The examples in this tutorial demonstrate pre-buffered ads for seamless ad transitions. For background on CSAI concepts, techniques, and sync strategies, see Client-side ad insertion in Vega.
In this tutorial, you learn how to:
- Set up player client references and imports
- Set up the video surfaces for shared or dual surface mode
- Detect an ad marker and pre-initialize the ad player client
- Wait for the ad to buffer, then pause main content
- Switch the video surface and play the ad
- Return to main content after the ad ends
Prerequisites
- Vega development environment set up
- Vega SDK v0.22 or later
@amazon-devices/kepler-player-clientand@amazon-devices/kepler-player-serverpackages installed- Main content player client already initialized and connected to the service
- Basic knowledge of React Native and TypeScript
Set up player client references
Import the required packages and create refs for the main player client, ad player client, session IDs, and surface handles.Set up the video surfaces
Choose a surface mode. For the differences between the modes, see Surface modes.- Shared surface: Render one
KeplerVideoSurfaceViewand store its handle insurfaceHandleRef. Both player sessions use this surface in turn. - Dual surface: Render a second
KeplerVideoSurfaceViewon top of the main surface for the ad player session, and store its handle inadSurfaceHandleRef.
Detect the ad marker and pre-initialize the ad player client
When the position listener detects an upcoming ad break, pre-initialize the ad player client withautoPlay=false and register listeners to know when the ad is buffered and when it ends.
-
Set up a position listener to detect upcoming ad breaks.
-
Create the ad player client initialization function. Register a status listener to detect the READY and ENDED states. On platforms where
IPlayerSessionState.READYis not available, the service sends aplayerReadymessage as a fallback.
Wait for the ad to buffer, then pause main content
After the ad player signals READY (buffered) and the position listener detects the ad start time is reached, pause the main content.Switch the surface and play the ad
When the main content status changes to PAUSED, give the ad player session a surface and play the ad.- Shared surface: Clear the main session’s surface, then set the same surface on the ad session.
- Dual surface: Set the ad surface on the ad session. Don’t clear the main session’s surface.
Return to main content
After the ad ends, clear the ad surface, clean up the ad player client, and resume main content. In shared surface mode, set the surface on the main session again before you resume. In dual surface mode, the main session still has its surface.Clean up resources
When your component unmounts or the player session ends, unload the ad player client and release resources.Related content
- Client-side ad insertion in Vega
- Surface modes: shared and dual surface
- Implement client-side ad insertion using the JS approach

