关键术语和概念
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本部分介绍了这些指南中使用的一些关键术语,以及规范中使用的缩写。
“必须”“应该”和“可能”的含义
根据 IETF 发布的定义,Android for Cars 设计指南采用了必须、应和可以的术语。汽车制造商和应用开发者都需要了解这些术语的含义。
在这些指南中,以下术语必须、应和可以频繁出现(在表格中均采用大写形式,在连续文本中采用小写形式)。这些术语的用法符合 IETF 提供的定义,以阐明规范中的各种要求级别。
如需了解完整详情,请参阅 IETF 定义,这些定义是这些指南和 Android 兼容性定义文档 (CDD) 中关于这些术语用法的权威来源。
为了确保 Android for Cars 系统能够在所有实现中一致且可靠地运行,汽车制造商和应用开发者需要注意以下几点:
术语 |
含义 |
最低要求 |
该指南是绝对要求(不能省略或忽略)。此类要求在 API 级别或通过以下方式强制执行:
- Google 针对使用 Google 汽车服务的汽车制造商提供的设计审核流程
- Google Play 商店对第三方应用的审核流程
|
应当有 |
在某些情况下,有的理由可以忽略该指南,但是在选择其他课程之前,您必须了解并仔细权衡所有影响。
|
可以 |
该指南并非完全强制性要求。一家汽车制造商或应用开发者可能会选择遵循这些指南来满足特定市场或产品需求,而另一家可能会省略同一项内容。
不包含特定选项的实现必须准备好与包含该选项的其他实现进行互操作,但功能可能会有所减少。同样,包含特定选项的实现必须准备好与另一个不包含该选项的实现(当然,此选项提供的功能除外)进行互操作。
|
驾驶状态
这些准则偶尔会涉及因汽车的驾驶状态(即汽车处于停车、空档还是行驶状态)而异的用户体验差异。在不同驾驶状态和速度范围下允许行驶的物品取决于汽车制造商和不同地区的相关监管要求。
例如,在某些情况下,可能只允许在开启手刹时停止汽车执行特定操作。在其他情况下,只有在汽车以或低于特定速度(例如 5 英里/小时)行驶时,才允许执行该操作。
布局标签
在这些指南中,我们在描述规范布局时会用到以下标签。
标签 |
说明 |
 |
边缘:指示可用窗口的宽度和高度边界。
|
 |
外边距:定义应用画布的左侧和右侧边界,从最近的边缘测量。如需查看有关外边距宽度如何随屏幕尺寸变化的讨论,请访问应用工作空间。
|
 |
框线:一个与屏幕宽度成正比的值,用于指定某个元素与最近的外边距或组件边缘之间的水平距离。如要查看与特定屏幕宽度类别相关联的框线值,请访问框线。
|
 |
内边距:用于根据元素之间的关系指定屏幕上元素之间的间距的值。一般而言,两个元素之间的关系越小,内边距就越窄。如需详细了解规范布局中使用的内边距值,请访问 padding。
|
 |
Flex::用于指定容器内垂直或水平居中的元素,或可根据相邻元素扩大或收缩的距离。如扩缩策略中所述,灵活布局尺寸有时会被分配最小值或最大值。 |
 |
角半径:指定角的曲度,0 表示方角,值越大表示圆角越大。
|
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis document clarifies key terms like MUST, SHOULD, and MAY, aligning with IETF definitions for consistent understanding across car makers and app developers.\u003c/p\u003e\n"],["\u003cp\u003eDriving state context is crucial, as the car's state (parked, idling, moving) influences permissible actions and user experience, subject to car maker decisions and regional regulations.\u003c/p\u003e\n"],["\u003cp\u003eLayout labels like Edge, Margin, Keyline, Padding, Flex, and Corner Radius are used throughout the guidelines to illustrate specifications for app design and screen elements.\u003c/p\u003e\n"],["\u003cp\u003eFor in-depth information, refer to linked resources detailing IETF definitions, Android Automotive library, and layout specifications.\u003c/p\u003e\n"]]],[],null,["# Key terms & concepts\n\n\u003cbr /\u003e\n\nThis section explains some key terms used in these guidelines, as well as the abbreviations used in the specs.\n\n*** ** * ** ***\n\nMeaning of Must, Should \\& May\n------------------------------\n\nThe Android for Cars design guidelines use the terms **MUST** , **SHOULD** , and **MAY** according to definitions published by the IETF. Both car makers and app developers need to understand the meanings of these terms.\n\nThroughout these guidelines, the terms **MUST** , **SHOULD** , and **MAY** appear frequently (both capitalized in tables and lowercase in running text). The use of these terms conforms to the definitions provided by the IETF to clarify various requirement levels in specifications.\n\nFor full details, see the IETF definitions, which are the authoritative source for the way these terms are used in these guidelines and in the Android Compatibility Definition Document (CDD).\n\nTo ensure that Android for Cars systems work consistently and reliably across all implementations, car makers and app developers need to keep the following in mind:\n\n| Term | Meaning |\n|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| MUST | The guideline is an absolute requirement (cannot be omitted or ignored). Such requirements are enforced either at the API level or by: - Google's design review process for car makers using Google Automotive Services - Google Play store's review process for third-party apps |\n| SHOULD | There may be valid reasons in particular circumstances to ignore the guideline, but the full implications must be understood and carefully weighed before choosing a different course. |\n| MAY | The guideline is truly optional. One car maker or app developer may choose to follow the guidelines to meet specific market or product needs, while another may omit the same item. An implementation that does not include a particular option **MUST** be prepared to interoperate with another implementation that does include the option, though perhaps with reduced functionality. In the same vein, an implementation that does include a particular option **MUST** be prepared to interoperate with another implementation that does not include the option (except, of course, for the feature the option provides.) |\n\n[IETF definitions of MUST, SHOULD, MAY\nand related terms](https://www.ietf.org/rfc/rfc2119.txt)\n\n*** ** * ** ***\n\nDriving states\n--------------\n\nThese guidelines occasionally refer to differences in the user experience that depend on the car's driving state -- that is, whether it's parked, idling, or moving. The decisions about what is allowed in various driving states and speed ranges depend on the car maker and on the relevant regulatory requirements in different regions.\n\nIn some cases, for example, a certain action might be allowed only if the car is stopped with the parking brake on. In others, the action might be allowed only if the car is moving at or below a certain speed, such as 5 mph. \n[Android Automotive Library: android.car.drivingstate\nAdditional technical details for developers](https://developer.android.com/reference/android/car/drivingstate/package-summary)\n\n*** ** * ** ***\n\nLayout labels\n-------------\n\nThe following labels are used throughout these guidelines in depictions of spec layouts.\n\n| Label | Description |\n|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | **Edge:** Indicates width and height boundaries of the available window. |\n| | **Margin:** Defines the left and right boundaries of the app canvas, measured from the nearest edge. For a discussion of how margin width varies with screen size, visit [App working space](/cars/design/automotive-os/design-system/layout#app_working_space). |\n| | **Keyline:** A value that is proportional to screen width, used to specify the horizontal distance between an element and the nearest margin or component edge. For the keyline values associated with specific screen-width categories, visit [Keylines](/cars/design/automotive-os/design-system/layout#keylines). |\n| | **Padding:** Value used to specify spacing between elements on the screen according to their relationships. In general, the closer the relationship is between two elements, the narrower the padding. For details of the padding values used in spec layouts, visit [padding](/cars/design/automotive-os/design-system/layout#padding). |\n| | **Flex:** Term used to specify a vertically or horizontally centered element in a container, or a distance that can grow or contract according to the adjacent elements. Flex-layout dimensions are sometimes assigned a minimum or maximum value, as discussed in [Scaling strategies](/cars/design/automotive-os/design-system/layout#scaling_strategies). |\n| | **Corner Radius:** Specifies the curvature of a corner, with zero indicating a square corner and higher values indicating more rounding. |\n\n[Layout\nMargins, keylines, and padding for various screen sizes](/cars/design/automotive-os/design-system/layout)"]]