Lines Matching full:navigation
2 page.tags="navigation","layout","tablet"
10 navigation</li>
11 <li>Apps such as Gmail or the Play Store that combine a broad set of data views with deep navigation</li>
16 <p>A typical Android app consists of top level and detail/edit views. If the navigation hierarchy is
55 <p>Many apps focus on the content display. Avoid navigation-only screens and instead let people get to
64 The Play Store app's start screen primarily allows navigation into the stores for Apps, Music, Books,
93 <h4>Set up action bars for navigation and actions</h4>
98 <p>All screens in your app should display action bars to provide consistent navigation and surface
107 through the navigation hierarchy.</li>
116 well. Navigation supports switching between accounts and recent labels. Icons for creating a
124 <p>The top level communicates your app?s capabilities by introducing the user to the major functional areas. In many cases the top level will consist of multiple views, and you need to make sure that the user can navigate between them efficiently. Android supports a number of view controls for this task. Use the control that best matches your app's navigation needs:</p>
170 <h4>Navigation drawers</h4>
173 <p>A <em>navigation drawer</em> is a slide-out menu that allows users to switch between views of your app. It can hold a large number of items and is accessible from anywhere in your app. Navigation drawers show your app's top-level views, but can also provide navigation to lower-level screens. This makes them particularly suitable for complex apps.</p>
175 <p><strong>Use navigation drawers if</strong>:</p>
180 <li>You want to provide quick navigation to views which don't have direct relationships between each other.</li>
181 <li>You have particularly deep navigation branches.</li>
188 Navigation drawer from the Shopper app.
194 <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>
199 to the detail level, where data can be viewed and managed. Minimize perceived navigation effort by
201 <p>Even though the number of vertical navigation steps from the top level down to the detail views is
203 on the perception of onerous navigation.</p>
208 experience than to an explicit navigation step.</p>
309 <h4>Make navigation between detail views efficient</h4>
336 <p>Use action bars to provide consistent navigation.</p>
339 <p>Keep your hierarchies shallow by using horizontal navigation and shortcuts.</p>
345 <p>Allow for quick navigation between detail items with swipe views.</p>
