Skip to main content

App Structure and Behavior Model

Pleos Connect provides a vehicle-specific multi-window environment that displays the Driving view alongside an app area, where up to two apps can be placed. Because the area displayed and screen orientation of an app may change, app developers must consider a screen configuration and app lifecycle that differ from those of a mobile environment.

Screen Layout and Multi-window Support​

The Pleos Connect screen consists of a Driving view area that provides vehicle information to the driver and an area for displaying apps. The Driving view is displayed in a fixed area near the driver and cannot be hidden or terminated by an app. The app area is divided into one or two windows depending on the vehicle and display configuration.

Portrait and Landscape Screen Models​

In Pleos Connect, an app is displayed in portrait or landscape form depending on the window area it occupies.

  • portrait: A screen layout in which an app uses one window in the app area. When two apps are displayed simultaneously, each app is generally displayed in portrait.
  • landscape: A screen layout in which one app expands across two app areas. The app can use the wider screen to provide additional information or expanded content.
  • Design screens for both portrait and landscape.
  • In portrait, provide core functions and key information. In landscape, use the expanded area to provide additional information and extended functions.

App Launch and Window Transitions​

When a new app is launched or the window state of the current app changes, the app's display position and screen orientation may change. Detailed window placement and transition behavior may vary depending on the vehicle and display configuration.

  • A new app is displayed based on the screen orientation of the currently displayed app. If one landscape app is displayed, the new app also launches in landscape; if two portrait apps are displayed, the new app launches in portrait in the primary window.
  • An app that disappears from the screen is not necessarily terminated. It may remain in the background, and when a displayed app is terminated, recently used apps may be displayed again in the window order. Design the app to handle a transition back to the foreground.
  • Users can change the position and size of an app using the window bar or gestures. Design the screen flexibly so that core functions remain usable when the window size changes.

Screen Orientation and Size Adaptation​

In Pleos Connect, the number of windows used and the screen size vary according to the Activity's screen orientation setting.

  • If screenOrientation is not specified, the Activity runs in portrait by default and uses one window.
  • If screenOrientation is set to landscape, the Activity can use two window areas.
  • Design both portrait and landscape screens so that the priority and placement of content change naturally when the screen transitions.
  • Use responsive layouts so that the layout does not break when the screen orientation or window size changes. Because screen orientation is based on the screenOrientation setting in AndroidManifest.xml, review this setting together with the app's screen design.

Foreground/Background Transitions and Behavior Design​

Pleos Connect apps may frequently switch between foreground and background due to screen splitting, window position changes, launching other apps, and changes in driving conditions. Consider that an app that disappears from the screen may remain in the background without being terminated.

  • Restore the current state when entering the foreground and reconstruct the UI to match the screen size and orientation.
  • When entering the background, clean up work that can be stopped immediately, such as screen updates, animations, and unnecessary sensor collection.
  • For work that continues in the background, such as audio playback, communication, and downloads, clearly define the execution conditions and pause/resume policy for each task.
  • Minimize unnecessary background residency, timers, polling, and network requests to conserve vehicle system resources.
  • Establish a state-storage strategy so that user data and progress can be restored even when the app is terminated or its process is recreated.