Lines Matching refs:to
6 introduced significant changes to the global navigation behavior. Thoughtfully following the
16 <p>The Up button is used to navigate within an app based on the hierarchical relationships
17 between screens. For instance, if screen A displays a list of items, and selecting an item leads to
19 returns to screen A.</p>
23 <p>The system Back button is used to navigate, in reverse chronological order, through the history
30 button can return the user to the Home screen, or even to a different app.</p>
34 <p>The Back button also supports a few behaviors not directly tied to screen-to-screen navigation:
43 <h4>Navigating to screens with multiple entry points</h4>
46 in your app. In this case, the Up button should choose to return to the referring screen, behaving
47 identically to Back.</p>
60 <p>When your app supports navigation from a list of items to a detail view of one of those items, i…
61 often desirable to support direction navigation from that item to another one which precedes or
62 follows it in the list. For example, in Gmail, it's easy to swipe left or right from a conversation
63 to view a newer or older one in the same Inbox. Just as when changing view within a screen, such
68 <p>However, a notable exception to this occurs when browsing between related detail views not tied
71 history, causing the Back button to step through each previously viewed screen. Up should continue
72 to bypass these related screens and navigate to the most recently viewed container screen.</p>
76 <p>You have the ability to make the Up behavior even smarter based on your knowledge of detail
78 Book viewed to the details for the Movie adaptation. In that case, Up can return to a container
85 <p>You can use Home screen widgets or notifications to help your users navigate directly to screens
87 both bypass the Inbox screen, taking the user directly to a conversation view.</p>
93 app</em>, Up should navigate to that screen.</li>
94 <li><em>Otherwise</em>, Up should navigate to the topmost ("Home") screen of your app.</li>
98 task's back stack the complete upward navigation path to the app's topmost screen. This allows users
99 who've forgotten how they entered your app to navigate to the app's topmost screen before
102 <p>As an example, Gmail's Home screen widget has a button for diving directly to its compose
103 screen. Up or Back from the compose screen would take the user to the Inbox, and from there the
104 Back button continues to Home.</p>
110 <p>When your app needs to present information about multiple events simultaneously, it can use a
111 single notification that directs the user to an interstitial screen. This screen summarizes these
112 events, and provides paths for the user to dive deeply into the app. Notifications of this style are
116 interstitial screen returns the user to the point the notification was triggered from—no
119 navigating within the app rather than returning to the interstitial.</p>
123 events. Touching Back from the interstitial returns the user to Gmail. Touching on a particular
124 event takes the user away from the interstitial and into the full Calendar app to display details of
125 the event. From the event details, Up and Back navigate to the top-level view of Calendar.</p>
134 Talk uses this style to alert the user of an invitation from a friend to join a video chat, as this
146 <p>One of the fundamental strengths of the Android system is the ability for apps to activate each
147 other, giving the user the ability to navigate directly from one app into another. For example, an
148 app that needs to capture a photo can activate the Camera app, which will return the photo
149 to the referring app. This is a tremendous benefit to both the developer, who can easily leverage
153 <p>To understand app-to-app navigation, it's important to understand the Android framework behavior
162 <p>A <strong>task</strong> is the sequence of activities a user follows to accomplish a goal. A
166 <p>An <strong>intent</strong> is a mechanism for one app to signal it would like another
168 they can respond to. For common intents such as "Share", the user may have many apps installed
171 <h4>Example: navigating between apps to support sharing</h4>
174 to share content by using another app. For example, launching the Play Store app from Home begins
176 to see its details, the user remains in the same task, extending it by adding activities. Triggering
178 which have registered to handle the Share intent.</p>
182 <p>When the user elects to share via Gmail, Gmail's compose activity is added as a continuation of
186 <p>From the compose activity, sending the message or touching the Back button returns the user to
187 the book details activity. Subsequent touches of Back continue to navigate back through the Play
192 <p>However, by touching Up from the compose activity, the user indicates a desire to remain within
194 always rooted to Home, so touching Back from the conversation list returns there.</p>
198 <p>Task A persists in the background, and the user may return to it later (for example, via the
202 <p>When your app registers to handle intents with an activity deep within the app's hierarchy,
203 refer to <a href="#into-your-app">Navigation into Your App via Home Screen Widgets and
204 Notifications</a> for guidance on how to specify Up navigation.</p>