Create settings (optional)

If you want to make your app settings available to users on the car screen, you need to design a settings experience, plus flows for any error-handling that may be needed.

On Android Auto, settings for the car screen are not essential, since the app is projected from a phone that should already have its own settings experience. However, if you create settings as described below, they can potentially work for both AAOS and Android Auto.

You can create settings for the car screen using templates from the Android for Cars App Library, which are vehicle-optimized. The design process involves these tasks:

  • Choose settings to feature, including only those that are necessary for app use or relevant to in-vehicle user journeys
  • Organize your settings on the List template for easy navigability, making all settings available on a single screen if possible
  • Plan dialogs and error flows as needed, using templates such as the Message template
  • Validate usability, making sure your settings experience meets the UX requirements for the Android for Cars App Library

To learn more about designing with the templates, see Build apps with templates.

As you design your settings flow, keep in mind the requirements and recommendations below.

Settings examples

In AAOS, the app bar in the media app template includes an option for a Settings control, which users can select to bring up an overlay with your app settings screen.

Settings view
Example Settings overlay on AAOS (landscape)
Settings view
Example Settings overlay on Android Auto
Settings view
Example Settings overlay on AAOS (portrait)

Settings requirements

Requirement level Requirements
SHOULD App developers should:
  • Keep settings simple and easy to navigate
  • Include only settings that are necessary for app use (such as account info, app preferences, and sign-in/sign-out) or relevant to listening to media in the car (for example, turning off explicit content)
  • Make all settings accessible from a single screen, if possible
  • Avoid use of dialogs beyond simple confirmation

Rationale

  • Design for cars: Keep in-car settings to the minimum required for that environment, and make them easy to find and use.