应用布局
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。

在设计 Wear OS 应用时,请谨慎选择适合的布局
。由于 Wear OS 在圆形显示屏上运行,
规范布局分为两类
您在设计应用时应该考虑的指标
非滚动布局侧重于一目了然的信息,通过
互动很少或根本没有互动。因此,要构建
转换为这些布局:

- 针对语言、字体缩放、设备和可变组合进行测试
内容。
- 仅当内容已知或受控时使用不可滚动布局
或者必须使用特定的设计
- 对布局应用建议的上外边距、下外边距和侧边外边距。
- 在内容原本可能出现的位置,以百分比值定义外边距
进行裁剪。
- 合理排列元素,以充分利用空间内的空间
并在不同尺寸的设备之间取得平衡。
网页内容包含的信息过多,无法全部显示在一个屏幕上,或
若要支持更长且更具沉浸感的体验,请使用滚动条
视图。

采用响应式设计做法的滚动视图通常会适应一系列
屏幕尺寸。但在一些特殊情况下,您可以使用断点
覆盖尺寸并扩充布局,以显示其他选项,改进
或让内容更适合屏幕以下示例
显示了如何在大屏幕上加宽底部两个按钮:

Figma 设计套件
访问设计套件下载页面,探索内置
用于创建不同应用和功能块的组件、选项和建议
遵循最佳做法的设计。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-27。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# App layouts\n\nWhen designing apps for Wear OS, be intentional about the layouts you choose for\neach experience. Because Wear OS runs on circular displays and clipping is more\ncommon than on handheld devices, there are two categories of canonical layouts\nthat you should consider when designing your app.\n\nNon-scrolling app layouts\n-------------------------\n\nNon-scrolling layouts focus on glanceable information and offer users value with\nlittle or no interaction. Because of that, it can be challenging to build\nresponsive behavior into these layouts:\n\n### Build for responsive non-scrolling views\n\n- Test on a combination of languages, font scaling, devices, and variable content.\n- Use non-scrollable layouts only when the content is known or controlled ahead of time, or if you must use a specific design.\n- Apply the [recommended top, bottom, and side margins](/design/ui/wear/guides/components/dialogs#adaptive-layouts) to the layout.\n- Define margins in percentage values in places where content might otherwise be clipped.\n- Arrange elements to make the best possible use of the space within the screen and maintain balance across different device sizes.\n\nScrolling app layouts\n---------------------\n\nFor pages that contain more information than can fit on a single screen, or\nwhich are required to support longer and more immersive journeys, use a scroll\nview.\n\n### Build for responsive scroll views\n\n- Apply the [recommended top, bottom, and side margins](/design/ui/wear/guides/components/dialogs#adaptive-layouts).\n- Define outer margins in percentage values to prevent clipping at the beginning and end of the scrollable container.\n- Apply margins in fixed DP values between UI elements.\n\n### How to build for adaptive scroll views using a screen size breakpoint\n\nScroll views that use responsive design practices usually adapt to a range of\nscreen sizes. However, in some special cases, you can use a breakpoint to\noverride dimensions and augment layouts which show additional options, improve\nglanceability, or make content fit better on screen. The following example\nshows how, on larger screens, the bottom two buttons are widened:\n\nFigma design kits\n-----------------\n\n[Visit the design kit downloads page](/design/ui/wear/guides/foundations/download) to explore design layouts with built-in\ncomponents, options, and recommendations to create different app and tile\ndesigns that follow best practices."]]