[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Design for different form factors\n\nThe design of your app's UI isn't tied to a particular device form factor.\nAndroid applications need to adapt to a number of different types of devices,\nfrom 4-inch handsets to 50-inch TVs to ChromeOS devices with resizable windows.\n| **Note:** Designing applications for television sets also requires attention to other factors, including interaction methods (i.e., dealing with the lack of a touch screen), legibility of text at large reading distances, and more. You can find more information on designing for TVs in the [Android TV documentation](/tv).\n\nYour app's user interface is drawn inside of a window, the size of which can\nchange at will. You use resource qualifiers to provide different layouts for\nvarying window sizes. These differences can be due to constraints in the size of\nthe device's screen, or they can be driven by the user using multi-window mode\nto change the window size.\n\nDesigning responsive content\n----------------------------\n\nYou should provide a rich experience for all of your users, so you should have\neach screen in your app take full advantage of the window real estate available\nto you.\n\nFor example, an app running in a window taking up the full width of a phone\nscreen could perhaps hide details for a piece of content when entering\nmulti-window mode, and it could expand its user interface to provide more\ncontent when running in a window taking up the full width of a ChromeOS\ndevice's screen.\n\nIn addition to addressing these user expectations, it's often necessary to\nprovide more content on larger devices to avoid leaving too much whitespace or\nunwittingly introducing awkward interactions. In the following figure, you can\nsee some of the problems that can arise when adapting a user interface design\nfor a larger window:\n\n**Figure 1.** Not enough content on large-width windows leads to awkward whitespace and exceedingly long line lengths.\n| **Note:** After deciding at which window sizes you will provide difference resources, see [Providing Alternate Resources](/guide/topics/resources/providing-resources#AlternativeResources) for more detail on how to implement your designs.\n\nTo learn more about designing responsive navigation experiences, see [Navigation\nfor responsive UIs](/guide/topics/large-screens/navigation-for-responsive-uis).\n\nProviding tailored user experiences\n-----------------------------------\n\nIt's important to provide unique experiences that go beyond expanding your\ncontent views to fill available space. You can tailor user interfaces to provide\nthe ideal user experience for given window sizes, even using entirely different\nlayouts and widgets.\n\nIn figure 2, a\n[`BottomNavigationView`](/reference/com/google/android/material/bottomnavigation/BottomNavigationView)\nis used as top-level navigation when there is adequate vertical space to do so.\nWhen the size of the window is reduced, as shown on the right side of the\nfigure, top-level navigation is instead implemented using a\n[`DrawerLayout`](/reference/androidx/drawerlayout/widget/DrawerLayout).\n\n**Figure 2.** The bottom nav bar is replaced with a nav drawer when vertical\nspace is limited.\n\nHere are some other examples:\n\n- A [`Toolbar`](/reference/android/widget/Toolbar) can show or hide action menu items given the amount of available space.\n- A [`RecyclerView.LayoutManager`](/reference/androidx/recyclerview/widget/RecyclerView.LayoutManager) could change its span count to take full advantage of the size of a window\n- You can increase the amount of detail you show for custom views as you have more space to do so.\n\nThese are all great ways to make sure that your users have great experiences\nwherever they're running your app.\n\nYou can find more examples of responsive design patterns and ideas for adaptive\nlayouts on\n[material.io](https://material.io/design/layout/component-behavior.html#responsive-patterns)."]]