---
title: "Launching DIVA Player"
slug: "launching-diva-player"
updated: 2025-09-09T07:18:25Z
published: 2025-09-09T07:18:25Z
canonical: "documentation.deltatre.com/launching-diva-player"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.deltatre.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Launching DIVA Player

This article explains how the DIVA Player is launched from within integrated applications.

---

## How is DIVA Player launched?

Sitting within applications, DIVA Player launches when a user selects a call to action (CTA) or a video stream. DIVA’s unique interface takes control of the screen from the launch point, where video features are accessed.

### Select a video from an integrated application or web page

DIVA Player launches when a video stream is selected (via a CTA, link, or entry point) from an integrated application. This action starts the *Instantiation process* and the video player interface displays.

Each time the video player launches, the Instantiation workflow repeats. For more information, see [Instantiation workflow and sessions](/v1/docs/launching-diva-player#step-2-player-instantiation-workflow-and-sessions). Before end users can consume the selected video, several further steps are carried out:

#### Step 1: Player launch

The host application instantiates DIVA by calling parameters. Developers integrate DIVA with their Host Application and set it up by providing *Settings,* and *VideoMetadata*, fitting their specific setup and video workflow. More on these parameters below.

The *Settings* file, allows integrators to enable/disable DIVA features and configure specific feature parameters.

The *Dictionary* file allows DIVA to localize the player experience and contains the supported label translations.

The *VideoMetadata* file contains all metadata about the video, including the title, description, thumbnails, video URL, etc.

> [!NOTE]
> **Note:**Additional parameters depend on project specifics, including further options, e.g., to open video streams from a specific moment in time via resume points and deep links. For additional technical configuration information, see the [DIVA Developer hub](https://divadocs.deltatre.net/).

#### Step 2: Player instantiation workflow and sessions

The Instantiation workflow is repeated each time the video player launches. The scenarios that determine the behavior of the workflows include:

#### Remaining in the same Player session

Part of the Instantiation workflow is repeated when switching videos within the video player, by selecting a video list or an alert; this is known as the *same DIVA session*. DIVA internally changes the current videoID and only redownloads the video data for the newly selected video.

#### Closing and reopening the Player

If users leave the video player and return to the original integrated application, the Instantiation workflow restarts upon the user selecting a video stream (this is considered a new DIVA session). Both the Configuration file and the Dictionary are re-downloaded.

💡 See our [DIVA feature articles](https://documentation.deltatre.com/docs/diva-video-player-features) for more information. For technical documentation, including SDKs and APIs, visit our [DIVA Developer hub](https://divadocs.deltatre.net/).