Get Started
Android Auto Design / Get Started
Intro
The Android Auto automotive platform stands out from phones, tablets, or smartwatches, as it provides users assistance while driving. This means that activities unrelated to driving should not be included in the Android Auto experience. Driving tasks should be simple with minimal interaction and easily accessible, allowing the user to focus on operating the vehicle.
To uphold these principles, Google regulates the content allowed in cars. The use cases for Android Auto are restricted to only support users while driving. In addition, Google has defined categories of approved usage scenarios and UI layouts that provide clear guidance for the user experience.
Google offers two distinct automotive platforms that can be used to create applications for:
- Android Auto: Phone-based infotainment system that’s projected onto the screens of compatible cars.
- Android Automotive OS (AAOS): Infotainment platform that car manufacturers can customize and incorporate into their vehicles. If they’re GAS partners, they can also integrate it with Google Automotive Services (GAS).
Foundation
- Android Auto applications are not standalone apps but extensions to existing Android apps, similar to Wear OS applications.
- Before starting product design and development, Google requires an approval process for the persona and use case. This approval process is in addition to the regular app review before a release in app stores.
- The features of Android Auto app extensions must align with one of Google’s predefined app types.
- The user interfaces of Android Auto apps follow predefined UI templates from Google, ensuring a consistent look and feel.
Google’s templates do not allow for any modifications to the user interface, such as adding an SAP Fiori styling (font or colors) or SAP Fiori specific UI controls, components, or patterns. - The Android Studio simulator can be used to evaluate and test the Android Auto UI and Android Auto applications.