title: Equivalent of startActivityForResult() with Android Architecture Navigation
body: <p>I have a workflow with 3 screens. From "screen 1" to access to "screen 2", the user must accept some kind of <em>terms and conditions</em> that I call in my picture "modal". But he only has to accept those conditions once. The next time he is on the first screen, he can go directly to screen 2. The user can chose to NOT accept the terms, and therefore we go back to "screen 1" and do not try to go to "screen 2".</p>
  
  <p><a href="https://i.stack.imgur.com/zWqMx.png" rel="noreferrer"><img src="https://i.stack.imgur.com/zWqMx.png" alt="App workflow"></a></p>
  
  <p>I am wondering how to do it with the new <a href="https://developer.android.com/topic/libraries/architecture/navigation/" rel="noreferrer">navigation component</a>. </p>
  
  <p>Previously, what I would do it:</p>
  
  <ul>
  <li>On screen 1, check if the user must accept the conditions</li>
  <li>If no, start "screen 2" activity</li>
  <li>If yes, use <code>startActivityForResult()</code> and wait result from the modal. Mark the terms as accepted. Start "screen 2"</li>
  </ul>
  
  <p>But with the navigation graph, there is no way to start a Fragment to obtain a result.</p>
  
  <p>I could mark the terms as accepted in the "modal" screen and start the "screen 2" from there. The thing is that to access to the screen 2, I need to do a network request. I do not want to duplicate the call to the API and processing its outcome in both "screen 1" and "modal". </p>
  
  <p><strong>Is there a way to go back from "modal" to "screen 1" with some information (user accepted the terms), using Jetpack navigation?</strong> </p>
  
  <p><em>Edit:</em> I currently get around it by using the same flow that Yahya suggests below: using an Activity just for the modal and using <code>startActivityForResult</code> from the "screen 1". I am just wondering if I could continue to use the navigation graph for the whole flow.</p>