Skip to main content

CCP & Rotary Controller Development Guide

The Center Control Panel (CCP) of a vehicle includes a Rotary Controller, dial, physical buttons, etc. This document applies to the development of in-vehicle apps that support CCP, providing policies for CCP support by app classification, mandatory requirements and exceptions for CCP in pre-installed apps, CCP review criteria, and a download link for the Pleos Connect CCP UX guideline document.

CCP Support Policy​

Pleos Connect apps are classified as follows, with different CCP support requirements applied for each classification.

  • User-installed apps: These are distributed through the Pleos App Market and installed by the user in the vehicle.
  • Pre-installed apps: These are pre-installed when the vehicle is released.
  • System apps: These are provided by being included in the system image by the platform or OEM, and cannot be installed or deleted by the user.

User-installed Apps​

For user-installed apps, the developer can choose whether to support CCP, and there are no restrictions on registering and distributing non-CCP-supporting apps in the Pleos App Market. However, non-CCP-supporting apps must be fully operable through touch alone to prevent them from becoming unusable in a non-CCP environment.

Pre-installed Apps​

Pre-installed apps must support CCP. Implement CCP integration according to the Pleos Connect CCP UX guideline.

Pre-installed App CCP Application Policy

Pre-installed App CCP Policy​

  • The pre-installed app contract must specify "CCP support" as a mandatory condition.
  • The app must support CCP-based operations (rotation, click, directional movement, etc.) from the initial release.
  • CCP input and screen focus movement must comply with the Pleos Connect CCP UX guideline.
  • Future updates must not omit or disable CCP functionality.
  • Pre-installed apps that do not support or incompletely support CCP will not be approved.

Pre-installed App CCP Application Exception Policy​

Pre-installed apps are not required to support CCP if they meet one or more of the following conditions. This must be specified in the contract.

  1. If the app's functionality is centered on static content, making CCP input unnecessary
    • No screen movement or focus-based operation required
    • Simple information display apps (e.g., fixed information panels, single-screen structures)
  2. If CCP implementation is technically restrictive, such as in browser apps or certain media apps
  3. If CCP use is inappropriate for UX or safety reasons, such as in games

Game App CCP Support Policy​

While pre-installed apps are generally required to support CCP, game apps may be exempt if CCP support is meaningless or impossible due to their nature.

Browser App CCP Support Policy​

Usability Assurance Requirements​

Pre-installed browser apps must comply with the following to ensure usability in vehicles with CCP.

  • CCP rotation → Scroll (up/down)
  • CCP click → Link/button selection
  • CCP left/right movement → Focus movement (applicable areas: address bar, bookmarks/tabs/home, back/forward, settings, basic menu)

CCP Support Area​

Pre-installed browser apps limit CCP support to the browser UI area, and do not require full CCP focus support for internal web page content. This is because unpredictable behavior may occur on complex web pages or where focus does not align with the HTML structure.

How to Disable CCP​

To disable CCP, add the following meta-data under the <application> element in the manifest file. (Note: use <application>, not <activity>.)

AndroidManifest.xml
<application
  ...
  <meta-data android:name="com.hmg.rotary.ROTARY_SUPPORTED" android:value="false" />
  />

CCP Review Policy​

Pre-installed apps that must support CCP undergo a CCP review before being registered in the Pleos App Market. Below are examples of review items and result criteria.

Review Item Examples​

The following items are checked during the review.

  • Whether focus movement works correctly on all major UI components
  • Whether list/menu scrolling is smooth with CCP rotation
  • Whether selection/confirmation input is performed correctly with CCP click
  • Whether reverse input (back, cancel) is processed correctly
  • Whether there are no areas where CCP operation is impossible due to touch-only UI
  • Whether safety-related actions (e.g., blocking elements while driving) are observed during CCP input

Review Result Criteria​

  • If the app passes the CCP test, it can be registered as a pre-installed app.
  • If the app fails the CCP test, it must incorporate the requested modifications and request a re-review.

Pleos Connect CCP UX Guideline​

CCP Policy Compliance Notes
  • CCP support policies may be updated according to AAOS version, vehicle platform, and vehicle model specifications.
  • CCP is directly related to vehicle safety, so non-compliance with HMI/safety standards may result in distribution restrictions or exclusion from pre-installed apps.
  • If the Pleos Connect CCP UX guideline is updated, pre-installed app developers may be requested to update their apps.