Lines Matching full:tabs
20 <li><a href="#tabs">Tabs</a></li>
29 <li><a href="{@docRoot}design/building-blocks/tabs.html">Android Design: Tabs</a></li>
55 <p>Descendant and lateral navigation can be provided using lists, tabs, and other user interface patterns. <em>User interface patterns</em>, much like software design patterns, are generalized, common solutions to recurring interaction design problems. We explore a few common lateral navigation patterns in the sections below.</p>
103 <h2 id="tabs">Tabs</h2>
108 href="{@docRoot}design/building-blocks/tabs.html">Tabs</a> guide.</p>
111 <p>Using tabs is a very popular solution for lateral navigation. This pattern allows grouping of sibling screens, in that the tab content container in the parent screen can embed child screens that otherwise would be entirely separate contexts. Tabs are most appropriate for small sets (4 or fewer) of section-related screens.</p>
114 <img src="{@docRoot}images/training/app-navigation-descendant-lateral-tabs.png"
115 alt="Example phone and tablet tab-based navigation interfaces with relevant screen map excerpt" id="figure-tabs">
120 <p>Several best practices apply when using tabs. Tabs should be persistent across immediate related
125 not re-select tab <em>A</em>. Tabs are usually laid out horizontally, although other presentations
128 appropriate. Lastly, and most importantly, <em>tabs should always run along the top of the
131 <p>There are some obvious immediate benefits of tabs over simpler list- and button-based navigation:</p>
135 <li>Users can navigate quickly between related screens, without needing to first revisit the parent. <p class="note"><strong>Note</strong>: when switching tabs, it is important to maintain this tab-switching immediacy; do not block access to tab indicators by showing modal dialogs while loading content.</p></li>
149 <p>Another popular lateral navigation pattern is horizontal paging, also referred to as swipe views. This pattern applies best to collection-related sibling screens, such as a list of categories (world, business, technology, and health stories). Like tabs, this pattern also allows grouping screens in that the parent presents the contents of child screens embedded within its own layout.</p>
158 <p>In a horizontal paging UI, a single child screen (referred to as a <em>page</em> here) is presented one at a time. Users are able to navigate to sibling screens by touching and dragging the screen horizontally in the direction of the desired adjacent page. This gestural interaction is often complemented by another UI element indicating the current page and available pages, to aid discoverability and provide more context to the user. This practice is especially necessary when using this pattern for lateral navigation of section-related sibling screens. Examples of such elements include tick marks, scrolling labels, and tabs.</p>
169 <p>Additionally, for sibling-related screens, horizontal paging is most appropriate where there is some similarity in content type and when the number of siblings is relatively small. In these cases, this pattern can be used along with tabs above the content region to maximize the interface's intuitiveness. For collection-related screens, horizontal paging is most intuitive when there is a natural ordered relationship between screens, for example if each page represents consecutive calendar days. For infinite collections (again, calendar days), especially those with content in both directions, this paging mechanism can work quite well.</p>