Lines Matching full:tabs
104 <h4>Fixed tabs</h4>
107 <p><em>Fixed tabs</em> display top-level views concurrently and make it easy to explore and switch between them. They are always visible on the screen, and can't be moved out of the way like scrollable tabs. <em>Fixed tabs</em> should always allow the user to navigate between the views by swiping left or right on the content area.</p>
108 <p><strong>Use tabs if</strong>:</p>
120 Default fixed tabs shown in Holo Dark & Light.
172 <p>After choosing the best top-level navigation for your app, don't mix and match patterns. For example, if you decide to use tabs for top-level switching, don't add a drawer, even if your navigation branches are deep. In this case, the navigation drawer would simply duplicate the information on the tabs, confusing your users.</p>
182 <h4>Use tabs to combine category selection and data display</h4>
193 <p>If the categories are familiar, predictable, or closely related, use scrolling tabs (where not all
194 items are in view simultaneously). Keep the number of scrolling tabs at a manageable level to
195 minimize navigational effort. Rule of thumb: no more than 5–7 tabs.</p>
199 The Play Store app uses tabs to simultaneously show category choice and content. To navigate
206 <p>If the categories in the tabs are not closely related, favor fixed tabs, so that all categories are
211 People uses fixed tabs to switch between different, relatively unrelated functional areas.
218 <p>For more discussion, see the <a href="{@docRoot}design/building-blocks/tabs.html">Tabs</a>
