Skip to content

App Control Seatback#

The App Control functionality in Seatback is part of the Pairing module. The initialization of the Pairing module has already been described in the Pairing use case document. The app launch feature allows the system to handle app or game launch and quit requests originating from the passenger’s electronic device.

The App Control Service only listens for launch and quit requests from the PED; it does not directly launch applications on the seatback monitor. The purpose of the App Control Service is to receive these requests from the PED within the Interactive application, and then the Interactive application uses the AppLaunchService (another service running on seatback) to actually launch or quit the app. For further details, please refer to App Launch Service’s developer document.

How to start with app control?#

To begin working with the App Control Service, the Pairing module must first be initialized. Once initialized, it provides an instance of the Pairing class. The Pairing class exposes the getAppControl() method, which returns an AppControl class instance. The AppControl class includes the necessary listeners and methods required for managing app control.

// Declare property
private Pairing mPairing;
private AppControl mAppControl;
Pairing.initService(activity, new IInFlightCallback() {
    @Override
    public void onInitServiceComplete(Object o, String s) {
        Log.v(TAG, "onInitServiceComplete() " + s);
        mPairing = (Pairing) o;
        mAppControl = mPairing.getAppControl();
    }

    @Override
    public void onInitServiceFailed(String s, InFlight.Error error) {
        Log.e(TAG, "onInitServiceFailed() " + s);
    }
}, new InFlight());

In the above example, once the Pairing module is initialized, the Pairing object provides a method to obtain an AppControl class instance.

How to capture app launch and quit requests sent from the passenger’s electronic device?#

The AppControl class provides a method to register a listener that listens for app control requests sent from the Passenger’s Electronic Device (PED). This listener interface defines two callback methods—one for handling app launch requests and another for handling app quit requests.

mAppControl.registerRequestListener(new AppControl.AppRequestsListener() {
    @Override
    public void onAppLaunchRequestReceived(String appIdentifier, boolean isVfsApp, Map<String, Object> appExtras) {
        // Method get invoke when app launch request received from PED
    }

    @Override
    public void onAppQuitRequestReceived(String appIdentifier, boolean isVfsApp) {
        // Method get invoke when app quiet request received from PED
    }
});

1. App Launch Request

The app launch request is received through the onAppLaunchRequestReceived method, which provides three parameters

  • appIdentifier : The app identifier will be the app or game media_uri if the application is part of the media kit (i.e., a VFS app). Otherwise, the identifier will be the Android application package name.

  • isVfsApp : If the app or game is part of the media kit, the value will be true; otherwise, it will be false.

  • appExtras : Some apps may require additional parameters - for example, a map application might need coordinates or a zoom level to display a specific location on the screen. These parameters are optional and are provided by the PED; therefore, the value may be null if not passed.

2. App Quit Request

The quit app is received through the onAppQuitRequestReceived method, which provides two parameter.

  • appIdentifier - The app identifier will be the app or game media_uri if the application is part of the media kit (i.e., a VFS app). Otherwise, the identifier will be the Android application package name.

  • isVfsApp : If the app or game is part of the media kit, the value will be true; otherwise, it will be false.

Note : To launch a media kit (VFS) app or game, the appLaunchService requires the configuration (cfg) file name. This file name can be retrieved by calling the Content Discovery service’s getItemDetails method. The getItemDetails method requires the media_uri, which is provided by the PED, and additionally the filename must be included in the request_fields parameter of the request.

How to send app status to PED?#

The AppControl service defines various AppStatusType values to represent the current state of an app on the seatback. Through its methods, these status updates can be communicated to the Passenger’s Electronic Device (PED), ensuring synchronization between the PED and the seatback-for example, when an application is launched, quit, or encounters an error during launch.

AppStatus appStatus = new AppStatus("game:tl1234bddd", "game", AppStatusType.LAUNCHED");
appStatus.setVfsApp(true);
mAppControl.sendAppStatus(appStatus);

The above example demonstrates how the app status is sent from the seatback through the interactive service. The AppStatus class is used to configure the status message. Its constructor requires three parameters: the app identifier (which may be the app or game media_uri for VFS apps, or the package name for Android apps), the content type (retrieved using the Content Discovery service’s getItemDetail method), and the AppStatusType enum provided by the AppControl service. Additionally, a boolean flag must be set to indicate whether the app or game is part of the media kit (VFS app); this should be set to true if applicable. Finally, the sendAppStatus method is used to notify the status to the PED.

When to send app status from Seatback to PED?#

The Interactive (INT) should send app status updates to the PED during the following events:

1. App Launch Request from PED

  • When a launch request is received from the PED, the app is started using the App Launch Service.
  • The App Launch Service provides a broadcast once the app is launching.
  • After receiving this broadcast, it is recommended to send a launch success event to the PED.

2. App Launched from Interactive

  • If the app is launched directly from the Interactive (instead of a PED request), and the PED is already paired with the seatback, the Interactive should still send the launch status to the PED.
  • The same broadcast from the App Launch Service can be used in this case as well.

3. App Quit (from Seatback or PED)

  • Whether the app quit is initiated from the PED or from the seatback, the Interactive must notify the PED.
  • Unlike app launch, the App Launch Service does not provide a quit broadcast.
  • When a quit request is received from the PED, the Interactive sends the quit command through the App Launch Service.
  • Once the app exits and the Interactive returns to the foreground, the Interactive should then send the quit event to the PED.

Why should the Interactive send app status?#

The PED relies on messages received from the seatback monitor. It listens to updates sent by the Interactive, such as the “Now Playing” information from the remote media player.

Although sending app status updates to the PED is not strictly required, it is recommended for a better user experience. These status updates allow the PED to display appropriate controls depending on the app type.

For example:

  • If a game is launched, the PED can present a game control screen.

  • If a map app is launched, the PED can provide navigation controls such as a D-pad or touchpad.

This ensures passengers can interact seamlessly with apps running on the seatback monitor.

Version 1.0