title: Why must a split view controller always be the root of any interface you create?
body: <p>In Apple's developer guide, they state: "A split view controller must always be the root of any interface you create" (<a href="http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/iPadControllers/iPadControllers.html" rel="nofollow">see here</a>). I was curious if anyone knew why they decided that. I have a tab navigator-based application and it makes sense for the content in one of the tabs to be presented in a split view. Why would Apple be opposed to that kind of design? Thanks in advance for your answers.</p>
  
  <p>-Max</p>
  
  <p>PS I'm not looking for ways to put a split view controller in a tab navigator controller (that much I can figure out, even if the code does look sloppy). I'm more curious if anyone has any idea why Apple frowns on it.</p>