Skip to main content

Minimizing Driver Distraction Elements

Optimized App Design for In-Drive Interaction​

To design an app that maintains continuous interaction with the driver while driving, it is necessary to adhere to design principles that minimize driver distraction. Be sure to review the Pleos Connect UI Design Guide guide for Pleos Connect before submitting your developed app. However, compliance with the provided guidelines does not guarantee the complete elimination of risks. If additional driver distraction risks are identified during the review, the app may be rejected.

Media App Design​

Apps containing media content should not be usable while driving, as they often include distractions.

If moved to the background and then resumed, the last used state should be restored.

  • The applied state may change depending on the time the user returns to the app.

    Returning within a few minutes: restore as closely as possible to the last used state. If not used for several hours, start from either the last used state or the default state.

All media apps must not be runnable or usable while driving.

  • Media apps refer to apps with video, game, or browser functionalities.
  • All media apps can only be used while stationary.

Media app usage should be paused when driving begins.

  • When driving starts, the app's UI should be hidden.
  • While driving, pausing restrictions for video, game, or browser apps must not be lifted.

Media apps should provide appropriate titles and thumbnails for all media items.

  • Titles and thumbnails should be structured for easy recognition.
  • Inappropriate content should not appear in titles, thumbnails, or previews.

    See Inappropriate Content for reference.

Media apps must not post heads-up notifications.

  • Notifications unrelated to driving cannot be used.

Video apps must be integrated with the media session.

  • Using multiple media simultaneously is not allowed.
  • Videos must support play/pause/stop commands based on content.

Browser apps must not store or allow access to passwords or payment information.

  • Except when users can block password access using profile lock.

If a browser app synchronizes passwords or payment data, it must comply with the following process.

  • Before synchronizing data with a vehicle, the following steps must be performed.
    • Display an authentication message to the user.
    • Inform the user via the vehicle screen that the data is being synchronized with the vehicle.