ApplicationLauncher Cluster

Cluster ID: 0x050C  |  Endpoint: Media endpoint (smart TV, set-top box, streaming device, etc.)

ApplicationLauncher handles launching, stopping, and hiding content apps on media devices — it is the underlying implementation for voice assistant commands like "Open Netflix" and "Close the current app". It manages the app lifecycle (launch/stop/hide), not in-app content playback. Typically deployed on the media endpoint of smart TVs or set-top boxes, used in conjunction with ApplicationBasic (app information queries).

Commands

The ApplicationLauncher Cluster has 3 request commands and 1 response command. LaunchApp launches an app, StopApp stops it, HideApp hides it (moves to background), and all three return LauncherResponse with the operation result. Click a command ID in the table below to jump to its detailed description.

LaunchApp — Launch App (0x00)

Launches the specified app on the device. If the app is already running, it is brought to the foreground. The target app is uniquely identified via ApplicationStruct, and can carry application-specific data (e.g., DeepLink, launch parameters).

// LaunchApp command example
// Launch the StreamCo Player app from the CSA catalog
{
  "Application": {
    "CatalogVendorID": 24742,
    "ApplicationID": "com.streamco.player"
  },
  "Data": "source=voice&deeplink=/home"
}

↑ Back to Commands

StopApp — Stop App (0x01)

Stops the specified app on the device. The app's runtime status changes to Stopped. If the app is playing content, playback is also terminated.

// StopApp command example
// Stop the currently running StreamCo Player app
{
  "Application": {
    "CatalogVendorID": 24742,
    "ApplicationID": "com.streamco.player"
  }
}

↑ Back to Commands

HideApp — Hide App (0x02)

Moves the app to the background without terminating its process. The app status changes to ActiveHidden, and it can still perform background tasks (e.g., continue playing music).

// HideApp command example
// Hide app (move to background, process not terminated)
{
  "Application": {
    "CatalogVendorID": 24742,
    "ApplicationID": "com.streamco.player"
  }
}

↑ Back to Commands

LauncherResponse — Operation Result (0x03)

Unified response for LaunchApp, StopApp, and HideApp. Contains a status code and optional additional data. Controllers determine success based on Status; on failure, Data may contain error details.

// LauncherResponse example
// Launch successful
{
  "Status": 0,
  "Data": "session-id=xyz789"
}

// App not available (not installed or not in catalog)
{
  "Status": 1,
  "Data": "Application not found in catalog"
}

// Waiting for user approval (e.g., first launch requires agreeing to terms)
{
  "Status": 3,
  "Data": "User approval required for first launch"
}

↑ Back to Commands

Attributes

The ApplicationLauncher Cluster has 2 attributes. Click an attribute ID in the summary table below to jump to its detailed description.

App Management (0x0000, 0x0001)

Describes the app catalog scope supported by the device and the current foreground app status.

↑ Back to Attributes

Struct Definitions

The ApplicationLauncher Cluster uses two structures to identify apps.

ApplicationEPStruct (App Endpoint Struct)

Describes an app and its corresponding Endpoint on the device. Used in the CurrentApp attribute, allowing Controllers to both know what the current foreground app is and directly locate its Endpoint for further interaction.

ApplicationStruct (App Identifier Struct)

Uniquely identifies a content app through the catalog system. This struct is used in LaunchApp / StopApp / HideApp commands and the CurrentApp attribute, and shares the same structure as the ApplicationBasic Cluster's Application (0x0004) attribute.

Enums

StatusEnum

Status codes in LauncherResponse, indicating the app operation result. Compared to ContentLauncher's StatusEnum, ApplicationLauncher's status codes cover app installation and permission approval scenarios.

Feature Bitmap

The ApplicationLauncher Cluster declares device capabilities via FeatureMap (0xFFFC):

Example Data

Attribute read results of the ApplicationLauncher Cluster from a smart TV with AP (ApplicationPlatform) enabled:

{
  // --- Supported App Catalogs ---
  "0x0000": [24742, 4996],           // CatalogList = supported catalog vendor ID list
                                      // 24742 = CSA official catalog
                                      // 4996 = an OTT platform catalog

  // --- Current Foreground App ---
  "0x0001": {                         // CurrentApp (current app, nullable)
    "Application": {                  //   ApplicationStruct
      "CatalogVendorID": 24742,       //     Catalog vendor ID (CSA official)
      "ApplicationID": "com.streamco.player"  //  App ID
    },
    "Endpoint": 3                     //   Endpoint number of the app
  }
}

Common Scenarios