title: How do I create a UINavigationController with a default "back" state?
body: <p>I have a <code>UINavigationController</code>, complete with table view and associated magic.</p>
  
  <p>The data I'm populating that table view from may have items from multiple categories, but the default view for the user will be one in which they are viewing <strong>all</strong> of the items, and then they have the ability to move backwards to a different table view that would allow them to select a different category, which would then return to the original table view with the appropriate data populated.</p>
  
  <p>What's the proper approach for this? I can't seem to wrap my head around how I would make the navigation controller give me a back button (with appropriately wired up actions) without having come from a previous view in the stack (which wouldn't really exist at launch time if I start the user off from what is essentially the detail view, in stack terms.)</p>
  
  <p>Also, the back button should be titled "Groups", not "Back", but that's really just an implementation detail. :)</p>
  
  <p><strong>Update:</strong> This issue finally manifested itself in production code, and here’s how I fixed it:</p>
  
  <p>My <code>UINavigationController</code> is created in a nib, with the root view set as the “groups” view. Then, in my app delegate, I push the second view onto the stack while the app is launching.</p>
  
  <p>That works fine for achieving the proper stack, but that doesn’t help with the back button title, because the navigation controller didn’t seem to want to grab the title from the root view, and instead was showing a back button with “Item” as the title.</p>
  
  <p>So, on the pushed view, in <code>viewDidLoad</code>, I set:</p>
  
  <pre><code>self.navigationController.navigationBar.backItem.title = @"Groups";
  </code></pre>
  
  <p>and that did the trick.</p>
  
  <p>The only potential downside of doing it this way would be if the pushed view controller were ever used in a scenario where the view below it wasn’t the groups view, but since the design of this particular application ensures that never happens, I’m accepting that failure. ;)</p>
  
  <p><strong>Another update</strong>:</p>
  
  <p>I’m an idiot. Just set the <code>title</code> property of the <code>navigationItem</code> provided by the <code>navigationController</code> in Interface Builder, and boom, no issue. Or do it in code. It doesn’t matter, just don’t do it by setting the <code>backItem.title</code> way I show you above. That’s just dumb.</p>