Stay organized with collections
Save and categorize content based on your preferences.
The process for designing apps in Android for Cars depends on the type of app
and its use case: whether it will be used while driving or while parked.
Some apps are designed using a set of templates spanning both driving and parked
use cases. Others, such as media apps, involve fitting your app content and
actions into a driving-optimized UI. Finally, for parked and passenger
experiences in cars with Google built-in, you can simply adapt an existing app
for the car screen.
As you design your app, keep in mind that
how users experience your app
will depend partly on whether they use the Android Auto version or the AAOS version (which is customizable by car makers). For more on who contributes what to the design, see
Partner roles.
[[["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 2024-07-23 UTC."],[[["Android for Cars app design varies based on usage (driving vs.parked) and app type."],["Templates are available for creating navigation, POI, IoT, and weather apps for Cars."],["Media apps require adapting content and actions to a driving-optimized UI."],["Existing video apps can be adapted for parked/passenger experiences in cars with Google built-in."],["User experience can differ between Android Auto and AAOS versions of an app."]]],[]]