打地基
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
两个 Android for Cars 系统的样式（Android Auto 和 Android Automotive OS (AAOS)）基于相同的互动设计和视觉设计原则。不过，这些系统的样式和布局详情在某些方面会有所不同，具体取决于每个系统的独特上下文。
下文概述了这些系统与样式相关的差异。如需详细了解各个样式和布局，请访问 Android Auto 设计系统和 AAOS 设计系统。
|
Android Auto |
AAOS |
| 样式上下文 |
- Google 构建和控制界面
- 界面从手机投影到车载显示屏
- 界面在所有汽车中都有相同的外观和风格
- 样式详情体现了 Google 品牌，并采用了应用品牌风格
|
- 汽车制造商基于 AAOS 构建界面
- 车载信息娱乐系统中内置了界面
- 界面是针对每种汽车型号量身定制的
- 样式详情体现了汽车制造商的品牌，并采用了应用品牌风格
|
| 样式和布局指南的用途 |
- 说明界面中样式选项背后的思考
- 为应用开发者可以做出的任何设计选择提供参考
|
- 解释为汽车制造商推荐的风格背后的思路
- 为汽车制造商提供关于为其界面创建自定义布局和样式的详细指南
- 为应用开发者可以做出的任何设计选择提供参考
|
| 主要区别 |
- Google 颜色
- 适用于较大字体的 Google Sans 字体
- 可适应各种汽车类型的 Google 确定布局
|
- 汽车制造商的颜色
- 适用于所有字体大小的标准字体（Roboto 或 Noto Sans）
- 自定义布局
|
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eAndroid Auto and Android Automotive OS share core design principles but differ in style and layout based on their unique contexts.\u003c/p\u003e\n"],["\u003cp\u003eAndroid Auto maintains a consistent Google-branded look across all cars, while AAOS allows car manufacturers to customize the UI to reflect their brand.\u003c/p\u003e\n"],["\u003cp\u003eDesign guidelines for Android Auto primarily explain Google's style choices, whereas AAOS guidelines provide more detailed guidance for car manufacturers creating custom layouts.\u003c/p\u003e\n"],["\u003cp\u003eKey style differences include color palettes, fonts, and layout adaptability.\u003c/p\u003e\n"]]],[],null,["# Style foundations\n\n\u003cbr /\u003e\n\nThe styles for the two Android for Cars systems -- [Android Auto](/cars/design/android-auto) and [Android Automotive OS](/cars/design/automotive-os) (AAOS) -- are based on the same [interaction design](/cars/design/design-foundations/interaction-principles) and [visual design](/cars/design/design-foundations/visual-principles) principles. However, the style and layout details for these systems differ in some ways, based on the unique context for each system.\n\nHere's an overview of the style-related differences between these systems. For details about styles and layouts for each, visit [Android Auto design system](/cars/design/android-auto/design-system/overview) and [AAOS design system](/cars/design/automotive-os/design-system/overview).\n\n| | Android Auto | AAOS |\n|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Style context | - Google builds and controls the UI - UI is projected from phone onto car screens - UI has same look and feel in all cars - Style details reflect Google brand, with app branding accents | - Car makers build the UI based on AAOS - UI is built into car infotainment systems - UI is customized for each car model - Style details reflect car-maker brand, with app branding accents |\n| Purpose of style and layout guidelines | - Explain the thinking behind the style choices in the UI - Serve as a reference for any design choices app developers can make | - Explain the thinking behind style recommendations for car makers - Provide detailed guidance for car makers creating custom layouts and styles for their UIs - Serve as a reference for any design choices app developers can make |\n| Key differences | - Google colors - Google Sans font for larger type sizes - Google-determined layout that adapts across car types | - Car-maker colors - Standard fonts for all type sizes (Roboto or Noto Sans) - Custom layouts |"]]
