第 3 层级:自适应且差异化
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
应用可利用在关键屏幕尺寸断点*处实现的新布局,专门针对屏幕尺寸打造用户体验,为屏幕较大的设备用户提供额外价值,从而提供小屏设备无法比拟的用户体验。
*在界面 (UI) 设计中,断点是指特定的屏幕宽度或视口大小,在该大小下,系统会更改内容的布局和呈现方式,以优化各种设备上的用户体验。开发者使用代码(例如 CSS 媒体查询)来定义这些点,建议您在设计规范中为这些断点提供两种设计。Wear OS 屏幕尺寸从 192dp 开始,大屏幕的默认断点为 225dp。
在 Wear OS 上使用断点
在 225dp 处使用断点 (BP) 有助于优化各种尺寸的布局。
check_circle
正确做法
- 在 225dp 或更高分辨率下设计自定义布局和行为,以使用额外的屏幕空间。
- 尽可能在断点后添加值。
- 在 BP 后面使用较大的组件选项,以便一目了然地查看界面。
- 富有表现力且大胆。
cancel
错误做法
- 仅针对一种设备尺寸进行设计。在多种屏幕尺寸上测试您的设计。
- 仅依赖响应式行为。
- 让您的应用或功能块平平无奇。
示例
以下图片展示了自适应且具有差异化的应用示例。
在 225dp 断点之后增加了主控件大小和底部按钮,从而增强了价值,更好地利用了较大屏幕上的额外空间,并提高了一目了然性。
在 225dp 断点后添加了一行按钮 - 通过额外的按钮增加了价值。
Picker
在 225dp 断点之后,数字会增大,以便更好地利用大屏设备上的额外空间,并提高一目了然的效果。
包含图表的卡片列表
在 225dp 断点之后增加了主数字和图表,以便更好地利用大屏幕上的额外空间,并提高一目了然的效果。
包含卡片的功能块
在 225dp 断点后添加了包含卡片的额外行,通过额外的卡片增强了价值。
Google 地图
在 225dp 断点后添加了包含卡片的额外行,通过额外的卡片增强了价值。
一目了然的通知
在 225dp 断点之后增加图片、应用图标和文字大小,以便更好地利用大屏幕上的额外空间并提高一目了然的效果。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Tier 3: Adaptive and differentiated\n\nApps that create a user experience specifically tailored to the size of the\nscreen, leveraging new layouts, implemented at a key screen size breakpoint,\\* to\nderive additional value for users of devices with larger screens, enabling a\nuser experience that devices with smaller screens can't match.\n\n\\**In user interface (UI) design, a breakpoint refers to a specific screen width\nor viewport size at which the layout and presentation of content are altered to\noptimize the user experience across various devices. Developers use code (like\nCSS media queries) to define these points, and it is advisable to supply two\ndesigns at these breakpoints in your design specs. Wear OS screen sizes start\nfrom 192dp with a default breakpoint for larger screens at 225dp.*\n\nUse breakpoints on Wear OS\n--------------------------\n\nEmploying a breakpoint (BP) at 225dp can help optimize layouts across a range of\nsizes. \ncheck_circle\n\n### Do\n\n- Design custom layouts and behaviors at 225dp+ to use the additional screen real-estate.\n- Add value after the breakpoint whenever possible.\n- Use the larger component options after the BP for a more glanceable UI.\n- Be expressive and bold. \ncancel\n\n### Don't\n\n- Design for just one device size. Test your designs across multiple screen sizes.\n- Only rely on responsive behavior.\n- Let your app or tile be unremarkable.\n\nExamples\n--------\n\nThe following images show examples of apps that are adaptive and differentiated.\n\n\n### Media player\n\nIncrease in main control sizes and additional bottom button after the 225dp\nbreakpoint - adding value, better utilizing the additional space on larger\nscreens and improving glanceability. \n\n\u003cbr /\u003e\n\n\n### Tile with button groups\n\nAdditional row of buttons after the 225dp breakpoint - adding value through\nadditional buttons. \n\n\u003cbr /\u003e\n\n\n### Picker\n\nNumbers increase in size after the 225dp breakpoint - better utilizing the\nadditional space on larger screens and improving glanceability. \n\n\u003cbr /\u003e\n\n\n### List of cards with graphs\n\nIncrease in main number and graph after the 225dp breakpoint - better utilizing\nthe additional space on larger screens and improving glanceability. \n\n\u003cbr /\u003e\n\n\n### Tile with cards\n\nAdditional row with a card after the 225dp breakpoint - adding value through\nadditional cards. \n\n\u003cbr /\u003e\n\n\n### Maps\n\nAdditional row with a card after the 225dp breakpoint - adding value through\nadditional cards. \n\n\u003cbr /\u003e\n\n\n### Glanceable notifications\n\nIncrease in image, app icon and text after the 225dp breakpoint - better\nutilizing the additional space on larger screens and improving glanceability. \n\n\u003cbr /\u003e"]]