[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003ePlan the structure of browsable content views, including the depth of levels, formatting (grid or list), and subcategory grouping.\u003c/p\u003e\n"],["\u003cp\u003eConsider implementing in-app search to enhance user experience and aid content discovery.\u003c/p\u003e\n"],["\u003cp\u003eLimit content hierarchy to a maximum of three levels to minimize driver distraction.\u003c/p\u003e\n"],["\u003cp\u003eUse subheaders when grouping content into subcategories within a view.\u003c/p\u003e\n"],["\u003cp\u003eChoose between grid and list formats for displaying content, ensuring the format aligns with the content type.\u003c/p\u003e\n"]]],[],null,["# Plan browsing views\n\n\u003cbr /\u003e\n\nWhen designing an app for browsing content, you'll need to plan what's in each\nview, as styling and navigation for browsing are handled by Google and the car\nmaker. Here are some considerations:\n\n- **Layers** \n\n How many levels of content do you want within your app? \n\n To minimize cognitive load, limit the total number of levels. Use subheaders\n to group content into subcategories within a view, which flattens hierarchy\n and improves navigation.\n\n- **Format** \n\n Do you want to display each level of content in either a grid format or a\n list format? A grid format displays multiple items displayed simultaneously\n in a grid-like arrangement, whereas, a list format (displays items\n vertically in a list).\n\n- **Grouping** \n\n Within each browsing view, do you want to group content into subcategories?\n This can help organize large amounts of content and make it easier for users\n to find what they're looking for.\n\n- **Searchability** \n\n When designing an app for driving, it is recommended to implement search\n capability. This allows users to quickly find specific content without\n having to navigate through multiple levels of browsing views.\n\nHow you define the root media item and its descendants establishes your app's\ncontent hierarchy. You can apply content styles to browsable media items to\ndetermine whether their children are displayed in grid or list views and whether\nthey are organized under titles.\n\nIf you implement in-app search, you won't need to design the voice and keyboard\nsearch interface, as car makers design both the voice search affordance and the\nkeyboards.\n\nFor more details, see\n[Supporting voice actions](https://developer.android.com/training/cars/media/#support_voice)\nand\n[Displaying search results](https://developer.android.com/training/cars/media/#display_search).\n\nBrowsing view examples\n----------------------\n\nIn this example, the designer uses a grid format to display music albums (Android Auto). This example uses a list, showing a combination of playlists and artists (Android Auto). This example uses a grid as well as a media control bar (AAOS). This example uses a list as well as a media control bar (AAOS). Two examples (list and grid) of media apps on AAOS (portrait)\n\n\u003cbr /\u003e\n\nBrowsing view requirements\n--------------------------\n\nKeep in mind the following requirements and recommendations:\n\n| Requirement level | Requirements |\n|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **MUST** | App developers must: - Provide subheader text if you decide to create subcategories within a browsing view |\n| **SHOULD** | App developers should: - Avoid browsable content that extends more than three levels deep from the top level - Decide whether to implement an in-app search function |\n| **MAY** | App developers may: - For each browsing view, determine whether to display content in a grid or in a list (list is the default) |"]]
