App Control Overview#
The App Control feature enables seamless communication between the PED (Passenger Electronic Device) and the Seatback system for launching and managing third-party apps or games.
There are two categories of apps in this flow:
-
Media Kit Apps (apps included in the media kit delivered with the system)
-
Non-Media Kit Apps (apps not bundled in the media kit, launched via identifiers such as package names)
Non-Media Kit apps use package names, with isVFS = false(Virtual File System), if the app/game is not part of the media kit.
When a user initiates an app launch from the PED, it sends the app details — such as the app identifier and optional parameters — to the Seatback system. For apps like a Map, additional optional parameters can be included — such as a target location and zoom level — which will be used by the Seatback system to open the app with a specific view or context. These extra parameters vary depending on the app type and its specifications. The Seatback then processes the request and launches the app accordingly. If the launched app is a game, the Companion App may automatically open a gamepad for interaction. The Seatback system also monitors the app’s lifecycle. When the app status changes (e.g., launched, quit, cancelled, or error), a notification is sent back to the PED. This ensures the PED UI is always in sync with the actual app status. App termination (quit) can be triggered either from the Seatback or from the PED. This bidirectional communication ensures a synchronized and controlled app experience for passengers, with flexibility for different app types and optional launch parameters.
Version 1.0