App Functionality and Performance Stability
Submitted apps must function properly and must not cause hardware/software damage or significant performance degradation. Additionally, all metadata for the submitted app must be accurate and up to date. Temporary files or content must be excluded from the app, and the submitted app must match the actual service content. Ensure all necessary steps have been completed before submission.
Completion and Performance
App Completion
Errors must not occur during app installation or removal.
- Major error examples
The app cannot be installed due to a missing authentication key. The app was installed, but files are missing. The app was uninstalled, but related files remained in storage or as icons.
Errors must not occur when running the app.
- Major error examples
The app force closes upon execution. Running the app causes the hardware to restart forcibly.
Errors must not occur when using app features.
- Major error examples
The screen freezes while using the app. The intended feature does not work. Touch or specific interactions are not recognized.
Media must play correctly during app usage.
- Major error examples
App audio cuts out intermittently. Graphics in the app are distorted.
The submitted app must be identical to the app that will be serviced.
- No dummy data or temporary files should exist in the app for testing purposes.
- Temporary content should not exist within the app.
Apps must display UI elements such as graphics, text, and images without distortion, blurring, or mosaic degradation.
The app must comply with device safe zones, including display cutouts, edge-to-edge insets, edge displays, software keyboards, and system bars.
- Consider UI safety zones, input methods, display cutouts, captions, and navigation menus.
Functionality and Performance
Submission may be rejected if the app includes functionality outside its category or if the selected type differs from the service content. The app must not malfunction or operate differently than intended.
The app must maintain stable performance without degradation.
- Severe performance degradation must not occur while using the app.
Performance degradation: stuttering, frame drops, screen tearing
- The app must not cause system performance degradation due to excessive resource usage.
Ensure the vehicle system response time does not exceed 0.25 seconds after input. Response time: The duration between a touch and the touch effect animation.
For app performance standards, refer to the App performance criteria guide.
The app must respond to user actions within a defined time frame.
- The app must launch within ten seconds.
- The app must load content within ten seconds.
- Specific buttons in the app must respond within two seconds.
Response means screen transitions, feature activation, or state changes.
- If a button action or content does not load within two seconds after user interaction, the UI must indicate app activity.
If the app is reopened after being sent to the background, it should restore the last used state.
- However, if unused for several hours, it may start in the default state.
Hardware or Software Damage
App usage must not cause damage to hardware or software. In addition to damage, actions that lead to performance degradation due to excessive resource consumption are also prohibited. Additionally, the app must not prompt users to restart the device or alter system settings that are unrelated to its core functionality.
SDK and API usage review
SDKs and APIs that can change vehicle state or affect driving safety are subject to separate review criteria for vehicle control and driving safety.
Vehicle SDK permission review criteria
- To use Vehicle SDK APIs, the permissions required for those APIs must be declared in the app.
- Vehicle SDK permissions may be declared only when pre-negotiated and approved with Pleos App Market.
- Apps that declare unapproved permissions cannot pass review.
Display Compatibility
The app must run according to the display specifications of the in-vehicle device. For detailed information on display compatibility, refer to the Display Layout guide.
Apps should maximize the display area without letterboxing.
- A slight letterbox in one direction (horizontal or vertical) may be allowed for minor aspect ratio adjustments.
- Apps must not run in compatibility mode.
When an app's resolution changes, it should not cause state loss or screen abnormalities.
- State loss: Loss of the screen or task the user was using
- Major abnormalities occurring during screen transitions
Image stretching Aliasing, blurring, and other quality deterioration Touch areas and button positions do not align
To maintain feature parity, the same functions and operations must be exposed in all screen states and transitions.
- Buttons or features should not change during screen transitions, and UI elements should move proportionally.