# Guidelines for custom screens

<br />

For most aspects of media apps used in Android Automotive OS, you do not 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](https://github.com/android/uamp/tree/master/automotive).

These general style guidelines apply to both custom settings screens and customized sign-in screens. They will help you to optimize your designs to be viewed on a car screen, while parked, at any time of day or night.

For additional guidelines specific to settings and sign-in, refer to [Design settings](https://developers.google.com/cars/design/automotive-os/apps/media/create-your-app/design-settings) and [Adapt sign-in flow](https://developers.google.com/cars/design/automotive-os/apps/media/create-your-app/adapt-signin-flow).
[![callout icon](https://developers.google.com/static/cars/design/common/images/default.svg)
Design system Guidelines on color, typography, sizing, and more](https://developers.google.com/cars/design/automotive-os/design-system/overview) [![callout icon](https://developers.google.com/static/cars/design/common/images/default.svg)
Design foundations Visual- and interaction-design principles for in-vehicle user interfaces](https://developers.google.com/cars/design/design-foundations/overview)

| Requirement level | Guidelines |
|---|---|
| **MUST** | App developers must: - Provide a Close affordance to exit the settings screen and top-level sign-in screen - Provide a Back affordance from any subsequent screens following the top-level screen - Position the Close or Back affordance at the top left of the screen - Maintain a [contrast ratio of at least 4.5:1](https://developers.google.com/cars/design/automotive-os/design-system/color#contrast) between backgrounds and icons or text - Use [recommended type sizes](https://developers.google.com/cars/design/design-foundations/visual-principles#make_content_easy_to_read) of at least 32dp for primary text and 24dp for secondary text - Keep touch targets above the [recommended minimum size](https://developers.google.com/cars/design/automotive-os/design-system/sizing#aligning_icons_and_touch_targets) of 76 x 76dp |
| **SHOULD** | App developers should: - Use a [dark theme](https://developers.google.com/cars/design/automotive-os/design-system/color#palettes_and_gradients) for all screens and overlays - Include a logo or app icon on all screens - When using an accent color, use the same one provided as a [branding element](https://developers.google.com/cars/design/automotive-os/apps/media/create-your-app/provide-branding-elements) - Keep text strings within the [recommended maximum text length](https://developers.google.com/cars/design/design-foundations/visual-principles#make_content_easy_to_read) of 120 characters - Provide a distance of at least 24dp between touch targets where possible |
| **MAY** | App developers may: - Decide whether to implement sign-in and settings functions as part of their app |

**Rationale:**

Screens designed directly by media app developers should

- Support standard media app navigation patterns and design conventions.

- Reflect design principles and visual foundations for Android Automotive OS.