title: Use Case with 2 ways for the same action
body: <p><strong>Question 1:</strong> What is the correct way to build a Use Case (or more than one) with 2 ways to do the same action?</p>
  
  <p>For example:</p>
  
  <p>I have a 3 screens in an iOS app:<br>
  1. A map view, which can be "long pressed" and has a camera button.<br>
  2. A camera view, which is shown if the user taps the camera button in the map view.<br>
  3. A place/pin editing view, which is shown if the user "long presses" the map view, or after the user chooses a photo in the camera view. This editing view has a save button to actually create the place with a photo and the location (long press coordinate or current location in case the camera button was presses).</p>
  
  <p>Title: Create Place
  Basic flow:<br>
   1. User “long press” on the map.<br>
   2. App drops a temporary pin and displays the place editing view.<br>
   3. User edits the place information and presses save button.<br>
   4. App creates the place and save it.<br></p>
  
  <p>Title: Create Place
  Basic flow:<br>
   1. User presses plus button.<br>
   2. App displays camera view.<br>
   3. User takes a picture.<br>
   4. App creates place with current location and picture.<br></p>
  
  <p><strong>UPDATE based on comments exchanged with bhavik.</strong></p>
  
  <p><strong>Question 2:</strong> (Based on bhavik's answer)<br>
  So I don't need one presenter for one interactor precisely, I can have 1 interactor and 3 presenters/views.</p>
  
  <ol>
  <li>In my case, I should have one presenter/view for the map, which is where it starts,<br></li>
  <li>then I should have one presenter/view for the camera, in case the user taps the camera button<br></li>
  <li>and one presenter/view for the editing view, in case the user "long presses" or after the user chooses the photo from the camera presenter/view and is redirected to the same editing view.</li>
  </ol>
  
  <p>Is that correct?</p>
  
  <p><strong>Question 3:</strong> Should my boundary methods for the interactor always return void?<br>
  In bhavik's example they are returning something, but in the <a href="http://www.objc.io/issue-13/viper.html" rel="noreferrer">VIPER blog</a> and <a href="http://youtube.com/watch?v=WpkDN78P884" rel="noreferrer">the uncle Bob's video</a> they always return void and the result comes in the form of another boundary method that the interactor calls on the presenter/controller.</p>
  
  <p><strong>Question 4:</strong> The VIPER way does not use a controller, only a presenter to talk to the interactor, when the uncle Bob's video uses a controller and a presenter for different interactions with the interactor. Which approach should I take?</p>
  
  <p><strong>Question 5:</strong> If my Use Case is something like "Go to other screen", should it even have an interactor? Since the current view will tell its presenter what button was pressed (what view to go to) and this current presenter will tell its wireframe "change to this other wireframe".</p>