In addition to making some decisions about how your content will be browsed and played (tasks 1 through 3), you may need to design app-specific screens for two functions: sign-in and settings.
If you want users to sign in to your app or access app settings, you need to design any relevant screens and interaction flows, including screens for any error-handling that may be needed. The examples and guidelines in this section will help you to optimize your designs to be viewed on a car screen, while parked, at any time of day or night.
To implement a settings function in your app, you need to declare a Settings activity in your app’s manifest file. Sign-in can be implemented either as a Settings workflow (if some functions of your app can be accessed anonymously) or as a dedicated Sign-in activity (if sign-in is required for using your app). For details, consult Add a Settings activity and Add a Sign-in activity.
Currently, you need to design the sign-in and settings screens for both portrait and landscape layouts:
A portrait-mode layout for the screen size used in the Volvo Polestar 2 (1068 x 1425dp; 1152 x 153px)
A landscape-mode layout for the screen size used in Google's reference Automotive implementation (1075 x 806dp; 1024 x 768px)
You can use the emulator in Android Studio to see how your layouts look in these two implementations. You can also consult Adaptive-responsive framework for reference information about how car makers’ layouts are adapted to various screen sizes (keeping in mind that details such as margins and padding values may be changed by the car maker).
If your app requires sign-in, Android Automotive OS will take users to your sign-in flow when they try to open your app without being signed in. After signing in, the user should land at the top level of your medica app’s navigation structure.
You need to design screens and a flow for whatever sign-in process your app uses, which will probably include one or more of the following:
Example screens and guidelines are provided below.
If you want users to sign in to your app by entering a username and password on the car screen, use the example below as a reference point and keep in mind the guidelines at the end of this section.
If you want users to use Bluetooth to connect with the phone version of your app for sign-in, use the example below as a reference point and keep in mind the guidelines at the end of this section.
If you want users to sign in using a PIN to connect via phone, use the example below as a reference point and keep in mind the guidelines at the end of this section.
Make all available settings accessible from a single screen
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)
Design for cars: Keep in-car settings to the minimum required for that environment, and make them easy to find and use.