添加功能块预览，以帮助用户查看 Wear OS 或手持设备上的功能块管理器中显示的内容。每个功能块都可以有 1 张代表性的预览图片。该图片应满足以下要求：
要求
以 400x400 像素导出资源。
提供圆形预览图片。
使用纯黑色背景。
另存为 PNG 或 JPEG。
为应用的常用语言添加本地化资源。
Wear OS 设备上的功能块管理器中显示的功能块预览。
手机上的功能块管理器中显示的功能块预览。
check_circle
正确做法
如果您要更新功能块中的信息（例如步数图表中的进度），请加以强调。
cancel
错误做法
显示空状态、在分页界面中显示功能块图标，或在功能块周围添加描边。
更大的屏幕尺寸
为了适应各种 Wear OS 屏幕尺寸，ProtoLayout Material 布局模板和 Figma 设计布局包含响应式行为，可让槽自动调整。槽的设计是为了填充可用宽度。主内容和辅助标签槽会紧贴内容，但容纳它们的容器会填满可用高度。边距设为百分比，并在屏幕底部和顶部的槽中添加额外的内边距，以考虑屏幕放大时曲线的波动。
[null,null,["最后更新时间 (UTC)：2025-07-27。"],[],[],null,["# Tiles design principles\n\nTiles provide quick access to information and actions users need to get things\ndone. After performing a swipe on the watch face, a user can see how they're\nprogressing toward their fitness goals, check the weather, and more. Users can\nalso launch apps and get essential tasks done quickly from tiles.\n\nUsers can choose what tiles they want to see on their Wear OS device, both from\nthe device itself and from the companion app.\n\nUX design principles\n--------------------\n\nThe system-provided tiles use a consistent design language, so users expect\ntiles to be each of the following:\n\n- **Immediate:** Tiles are designed to help users quickly complete frequent tasks. Display critical content in a clear information hierarchy so that users can understand the tile's content.\n- **Predictable:** Content within each tile should always focus on a user-facing task. This helps users predict what information they will be able to see on the tile, which improves recall.\n- **Relevant:** Users take their Wear OS devices wherever they go. Consider how the content in the tile is relevant to the user's current situation and context.\n\nApp icon\n--------\n\n| **Note:** The app icon is not displayed in any mocks that follow, since it's not part of the tile layout and might be added at a system level.\n\nThe app icon that may appear at the top of the screen is automatically generated\nby the system from the [launcher icon](/develop/ui/views/launch/icon_design_adaptive). Don't make this icon part of your tile's\nlayout. \ncheck_circle\n\n### Do\n\nWear OS may display the app icon automatically as the user scrolls through the tile carousel. There is no need to put the app icon in the tile design. \ncancel\n\n### Don't\n\nDo not add the app icon in the tile design as it may appear twice or overlapped if also displayed at the system level.\n\nDesign guidance\n---------------\n\nKeep the following guidelines in mind when creating tiles.\n\n### Focus on a single task\n\ncheck_circle\n\n### Do\n\nFocus each tile on a single task, such as **start run.** \ncancel\n\n### Don't\n\nSupport too many different tasks on a single tile.\n\n### Create separate tiles for each task\n\nIf your app supports multiple tasks, consider creating multiple tiles for each\ntask your app supports. For example, a fitness app could have both a goals tile\nand a workout activity tile.\n\n### Show glanceable representations of graphs and charts\n\ncheck_circle\n\n### Do\n\nShow quick, glanceable representations of numerical or statistical information and allow the user to tap to see more in an app if needed. \ncancel\n\n### Don't\n\nShow detailed numerical or statistical information on the tile.\n\n### Indicate latest data updates\n\nMake it clear to users how recent a tile's data is. If you show cached data,\nindicate when it was last updated.\n\n### Use an appropriate data refresh rate\n\nChoose an appropriate update rate for your tiles, considering the impact on\ndevice battery life. If you're using platform data sources such as heart rate\nand step count, Wear OS controls the update rate for you.\n\nEmpty states\n------------\n\nTiles have two types of empty states. For both, use\n[`PrimaryLayout`](/reference/androidx/wear/tiles/material/layouts/PrimaryLayout).\n\n\n**Errors or permission**\n\nTell the user that they need to update their settings or preferences from the\ntile. \n\n**Sign in**\n\nProvide a clear call to action on a sign-in tile.\n\n\u003cbr /\u003e\n\nShow ongoing activities\n-----------------------\n\nWhen an app performs a long-running activity---such as tracking a\nworkout or playing music---it should show the progress of the\n[ongoing activity](/training/wearables/notifications/ongoing-activity) in one of more tiles.\n\nIf your app also supports tiles that allow users to start these activities,\ndo the following to minimize user confusion:\n\n- Indicate that an ongoing activity is already in progress.\n- If the user taps on such a tile, launch your app and show the in-progress activity. Don't start a new instance of an ongoing activity.\n\n| **Note:** Typically, users can't stop an in-progress activity directly from a tile.\n\n### Required elements\n\n- **Primary data:** The main content that describes the activity.\n- **Label:** Displays the status of the activity.\n\n### Optional elements\n\n- **Icon or graphic:** Can be an animation or static image.\n- **Bottom compact chip:** Contains a call-to-action.\n\nMotion on tiles\n---------------\n\nWhen you add animations to tiles, help users understand changes: \ncheck_circle\n\n### Do\n\nEmphasize if you're updating information on a tile, such as progress toward a step count goal. \ncancel\n\n### Don't\n\nUnexpectedly toggle between values.\n\nPreviews\n--------\n\nAdd a tile preview to help your user see what content is shown in the tile\nmanager on their Wear OS or handheld device. Each tile can have one\nrepresentative preview image. That image should meet the following requirements:\n\n*** ** * ** ***\n\n\n**Requirements**\n\n- Export assets at 400px x 400px.\n- Provide a circular preview image.\n- Use a solid black background.\n- Save as a PNG or JPEG.\n- Add localized assets for your app's popular languages.\n\n\u003cbr /\u003e\n\n*** ** * ** ***\n\n\nA tile preview displayed in tile manager on a Wear OS device. \n\nA tile preview displayed in tile manager on a phone.\n\n\u003cbr /\u003e\n\n*** ** * ** ***\n\ncheck_circle\n\n### Do\n\nEmphasize if you're updating information on a tile, such as progress on a step count chart. \ncancel\n\n### Don't\n\nShow an empty state, show the tile icon in the pagination UI, or place a stroke around the tile.\n\nLarger screen sizes\n-------------------\n\nTo accommodate a variety of Wear OS screen sizes, the ProtoLayout Material\nlayout templates and Figma design layouts include responsive behavior, allowing\nthe slots to automatically adapt. Slots are designed to fill the available\nwidth. The main content and secondary label slots hug the content, but the\ncontainer holding them fills the available height. Margins are set as\npercentages, with additional inner margins added to slots at the bottom and top\nof the screen, accounting for fluctuations in the curve of the screen as it\nenlarges.\n\nTo maximize the larger screen size, use the additional space to provide more\nvalue by allowing users to access additional\ninformation or options. Achieving these layouts requires additional\ncustomization beyond the built-in responsive behavior, such as by creating an\nadditional layout with more content or by displaying previously hidden slots\nafter the breakpoint.\n\nNote that the recommended breakpoint is set at the 225dp\nscreen size.\n\n### Examples of how to design for a larger screen size\n\n#### Add buttons\n\n#### Add slots and content\n\n#### Add text"]]
