Driving Restriction Development Guide
Apps on Pleos Connect must apply in-vehicle UX restrictions based on the platform-provided CarUxRestrictions state. This guide explains how to integrate CarUxRestrictions and the key implementation considerations. For regional feature limits, see Driving Restriction Policy by Region. For UX design principles while driving, see Design Considering Driving Safety.
CarUxRestrictions integration
Apps obtain CarUxRestrictions through AAOS CarUxRestrictionsManager, check driving-restriction state, and implement behavior per specification.
After registering registerListener() with CarUxRestrictionsManager, receive updated CarUxRestrictions through the onUxRestrictionsChanged() callback.
For the availability of apps that do not declare Distraction Optimization (DO) in each driving situation, see Driving Restriction Policy by Region. Apps that declare DO must also check CarUxRestrictions and ActiveRestrictions when driving restrictions are active and apply feature-specific UX restrictions themselves.
Sample code
if (mCurrentCarUxRestrictions.isRequiresDistractionOptimization()
&& (mCurrentCarUxRestrictions.getActiveRestrictions()
& CarUxRestrictions.UX_RESTRICTIONS_NO_VIDEO) != 0) {
stopPlayingVideo();
}
Mapping UX rules to CarUxRestrictions
Apply feature-specific CarUxRestrictions flags based on the ActiveRestrictions of CarUxRestrictions received through the onUxRestrictionsChanged() callback.
- Example: for video (DMB), use
CarUxRestrictions.UX_RESTRICTIONS_NO_VIDEOto determine whether playback must be restricted while driving. - The UX restriction Figma specification is not published on Pleos Playground.
Because the platform delivers ActiveRestrictions according to the regional restriction specification, apps only need to apply the CarUxRestrictions received via notify.
For information about regional allow/lock rules for features such as keyboard and search, see Driving Restriction Policy by Region.