Guidelines for custom screens
Stay organized with collections
Save and categorize content based on your preferences.
For most aspects of media apps used in Android Automotive OS, you don't need to
design custom screens. The areas of exception are settings and sign-in. If you
want users to access app settings, you need to design settings screens. Also, if
your app requires sign-in, you need to provide a sign-in flow, which you can
customize from the sample code in the Universal Android Music
Player.
These general style guidelines apply to both custom settings screens and
customized sign-in screens. They help you to optimize your designs to be viewed
on a car screen, while parked, at any time of day or night.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-03-04 UTC."],[],[]]