Pleos Connect App Design Guide

This document provides essential guidelines to consider when converting a mobile app into a Pleos Connect app or designing a Pleos Connect app from scratch.

Pleos Connect App Design Guide

This document provides essential guidelines to consider when converting a mobile app into a Pleos Connect app or designing a Pleos Connect app from scratch.

Design Considering Driving Safety

Since apps running on Pleos Connect are intended to be used while driving, they must be designed with a UX that can be operated intuitively and stably with one hand so as not to distract the driver. Follow the AAOS Driver Distraction Guidelines and pay attention to the following principles in design and development.

Driving Restriction Policy by Region

If Driver Distraction Prevention (DO) is not declared in the app, whether the app can be used varies depending on the driving situation.

App Structure and Screen Model

Pleos Connect supports vehicle-optimized layouts such as multi-window and displaying two apps simultaneously.

Hardware Access Policy

Pleos Connect apps must access hardware only through platform APIs, and mobile-only APIs may be restricted in the in-vehicle environment. You must also design for potential network instability while driving.

SDK API Policy

This page describes Pleos Connect SDK API policies, including AAOS Alignment and backward compatibility.

API Compatibility & Availability

When designing and developing a Pleos Connect app, you must confirm in advance which APIs and AAOS vehicle properties are available on your target vehicle.

Design for Performance and Resource Efficiency

In an infotainment system, multiple apps run simultaneously, so it is important to be frugal with resource usage. You should design your app with fast startup and a light resident footprint in mind.

Design Considering Security and Privacy

Because vehicles are devices shared by multiple people, you must design your app with careful attention to security and privacy.