[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Common layouts for tiles\n\nTiles provide quick access to information and actions users need to get things\ndone. With a swipe from the watch face, a user can see how they are progressing\ntowards their fitness goals, check the weather, and more. Launch an app or get\nessential tasks done quickly from tiles.\n\nBuild responsive and optimized designs\n--------------------------------------\n\nTo help you adapt your design layouts to larger screen sizes, we have updated\nthe behavior of our layouts and components to have built-in responsive behavior,\nincluding percentage-based margins and padding.\n\nIf you are using our ProtoLayout templates, you can inherit these updates\nautomatically through the latest beta release of the [Wear ProtoLayout](/jetpack/androidx/releases/wear-protolayout)\nJetpack library. Also, you only need to supply layouts where you have added\nadditional content or components after a screen size breakpoint. For full\nguidance and recommendations on how to take advantage of a larger screen size,\nview our \\[tiles guidance\\]\\[2\\]. Tiles have a fixed screen height, so we've\nadjusted the padding to maximize the limited screen real estate without creating\nunwanted clipping.\n\nCheck that components fill the available width\n----------------------------------------------\n\n\nAll components should be built responsively. By setting the height and width to\n\"expand,\" they fill the available space. Include the necessary margins to\nprevent content from being clipped by the rounded screen. \n\n\n\u003cbr /\u003e\n\nBuild adaptive and differentiated designs\n-----------------------------------------\n\nTo make the most of the additional space on larger screen sizes, add a size\nbreakpoint at 225dp. This breakpoint lets you reveal additional content, include\nmore buttons or data, or change the layout to better suit the larger screen.\n\nThis requires a different design for each breakpoint. The larger screen design\n(225+ dp) could include the following additional elements:\n\n### Show the previously hidden title slot\n\n\nThis is advised on layouts with two rows before the breakpoint, where the title\nslot needs to be removed in order to ensure the min tap target of 48dp. \n\n\u003cbr /\u003e\n\n### Increase the size or change the state of the existing components\n\n\nThis could be done in order to show more detail or make the content more\nglanceable.\n**Note:** Don't just scale up the design. Instead, use components that respond and adapt to the available width and height. You could also use a different or larger component style, or graphic content with additional details. \n\n\u003cbr /\u003e\n\n### Add component slots within the current layout\n\n\nBy adding components, the layout provides more options or additional details.\nMake sure the content remains glanceable, though. \n\n\n\u003cbr /\u003e\n\n### Add more content at the bottom\n\n\nIn some cases, it makes more sense to add action buttons or content in the\nbottom section, rather than adding components within the main slot. \n\n\u003cbr /\u003e\n\n**Caution:** A larger display size should\n*never* display less information than ones that are smaller than it.\nThis is especially relevant for custom behaviors added in at the\nbreakpoint.\n\nA common example of this is when components or text sizes are increased\npast the breakpoint and end up showing less are the larger screens. Screens\nshould *always* show more value with increasing size.\n\nResponsive and adaptive behavior\n--------------------------------\n\nThe responsive and adaptive behavior depends on the three slots (sections) of\nthe layout.\n\n### App icon and title slot\n\nThere is no behavior change on the app icon that the system provides. The title\nslot automatically adapts to the wider screen size, displaying additional\ncharacters. There are proportional (percentage) internal margins on the top\nsection to avoid any clipping when the screen size increases.\n| **Note:** The title slot is optional and should be hidden before the 225dp breakpoint when using a layout with two rows in the main content section. This lets the tap targets in the main content area remain large enough on the smallest screens.\n\n### Main slot (components)\n\nAll components within the main slot should set their width and height to\n\"expand\" so that they automatically adapt to the wider screen size. There are\nproportional (percentage) internal margins on the main slot section---and each row\nwithin this slot in some instances---to avoid any clipping when the screen size\nincreases. If you use a combination of corner radius and layout, your main slot\nmight require larger margins.\n\n### Bottom slot\n\nThere is no behavior change in the bottom button or text, but the width of the\nbutton and text boxes automatically adapt to the wider screen size, and gain\ncharacters. There are proportional (percentage) internal margins on the bottom\nslot to avoid any clipping when the screen size increases. When no bottom slot\nis present, a default margin is added automatically.\nTiles that include a button in the bottom slot\n\n\u003cbr /\u003e\n\nTiles that include text in the bottom slot\n\n\u003cbr /\u003e\n\nTiles with no bottom slot\n\nCreate differentiated experiences\n---------------------------------\n\nOne fully customizable layout, with 60 or more permutations built into it,\nallows for practically limitless customization. Tiles are built on a slot-based\nsystem, so you can replace a slot from the canonical layout with any content or\ncomponent, and set the component to one of the many variants and color\ncombinations. In this case, maintain responsive behavior and follow our design\nrecommendations.\n\nThese customizations should be limited, and shouldn't deviate from the tile\ntemplate. This is to maintain consistency when users scroll through the tiles\ncarousel on their Wear OS devices."]]