Skip to main content

Maps/Navigation App Development Guide

This guide provides the requirements to consider when developing apps in the Maps/Navigation category that run on Pleos Connect. It guides the policies that Maps/Navigation apps must adhere to in order to ensure driver safety, prevent system conflicts, and provide a consistent user experience. This guide is applied as a review criterion when registering with the Pleos App Market.

Basic Policies​

  • Driver Safety First
  • Single Route · Single Navigation Principle
  • Minimize Operations While Driving
  • Category-based Function Restrictions
  • Compliance with Pleos Connect Platform and AAOS Standard API and UX Guide

Maps/Navigation App Category Declaration​

All apps must declare their app category mandatorily during development and registration.

Category Declaration​

To use the NaviContainer (fixed display area for navigation apps), it must be known whether the app running on the Home screen is a Navigation app, which is confirmed through app category information. Therefore, app developers declare the app category with an intent filter in the manifest file.

AndroidManifest.xml
<intent-filter>
    <action android:name="android.intent.action.MAIN" />
    <category android:name="android.intent.category.APP_MAPS" />
</intent-filter>

Category Specification When Registering with Pleos App Market​

The app category declared in the manifest file must also be reflected when registering with the Pleos App Market.

Category Mismatch Policy​

  • If the declared category does not match the actual functionality, the app will be immediately rejected during the review.
  • If the functionality changes during the app review, a re-review must be requested.

Pleos Connect Route Policy​

Single Route Policy (Route Exclusivity Policy)​

  • In the AAOS environment, only one Navigation app can have an Active Route status, so voice guidance and route output from multiple Navigation apps are not allowed.

    StatusDescriptionAllowed Scope
    Active RouteRoute GuidanceVoice · TBT Allowed
    Inactive RouteMap Exploration StateGuidance Prohibited
    BackgroundBackgroundAll Guidance Prohibited
    danger

    Providing route guidance in Inactive Route / Background status is a policy violation. However, in the case of OEM Navigation apps, safe driving information may be provided to respond to safety regulations.

  • This route exclusivity policy applies not only between Navigation apps but also between Navigation apps and Phone Projection.

  • To comply with the single route policy, use the following APIs that handle app focus and route ownership in AAOS.

Route Switching Policy​

Pleos Connect allows route switching of Navigation apps only in the following two cases:

  • Switching by explicit user selection
  • Switching due to an error or termination of the existing Navigation app

When switching routes, Navigation apps must implement the following:

  • Provide guidance that users can recognize during route switching.
  • Do not switch automatically without user consent.

Implementation of Minimizing Operations While Driving​

The following items must be prohibited or allowed for operation in Navigation apps while driving.

Prohibited Items While DrivingAllowed Items While Driving
Complex menu navigation (exceeding 3 depths)
Long list scrolling
Display of videos, animations, advertisements		Voice input
Single-touch based main functions
Selection of favorite destinations

UX Review Guide​

Navigation apps must meet the following UX requirements when registering with the Pleos App Market.

  • Compliance with Pleos Connect Platform and AAOS UX Guide
  • Meet the minimum size for touch areas
  • Always display key driving information
  • Prohibit full-screen pop-ups while driving

System Integration and Permission Policy​

System Integration​

  • It is recommended to use official APIs of Pleos Connect and AAOS.
  • The use of unofficial sensors/APIs is prohibited.

Permission Policy​

Navigation apps must request only the minimum necessary permissions and comply with the following policies.

  • Location Permission: Mandatory
  • Microphone: Allowed only for voice input
  • Unnecessary permission requests will result in rejection during the review.

Performance and Stability Review Criteria​

Navigation apps must meet the following performance and stability requirements.

  • Minimize delays during app launch and switching.
  • Operate stably even during long drives.
  • Occurrence of crashes or freezes will result in rejection during the review.

Security and Privacy Policy​

Navigation apps must comply with the following security and privacy policies.

  • Location data must be processed with encryption.
  • HTTPS communication must be used.
  • A privacy policy must be provided.
  • Unnecessary storage of location data is prohibited.

Prohibition Policy (Immediate Reject)​

The following will result in immediate rejection during the review.

  • Display of advertisements while driving
  • Inclusion of video or game elements
  • Simultaneous route guidance by multiple navigations
  • Provision of functions that violate category
  • Violation of OEM/AAOS policies