title: Why are umbrella frameworks discouraged?
body: <p>I want to distribute Framework A. Framework A depends on Framework B. I want a user of my framework to only need to include Framework A, but still have programmatic access to Framework B.</p>
  
  <p>Apple does this all the time using the concept of "Umbrella Frameworks", but there is this topic in the docs:</p>
  
  <blockquote>
    <p><strong>Don't Create Umbrella Frameworks</strong></p>
    
    <p>While it is possible to create umbrella frameworks using Xcode, doing
    so is unnecessary for most developers and is not recommended. Apple
    uses umbrella frameworks to mask some of the interdependencies between
    libraries in the operating system. In nearly all cases, you should be
    able to include your code in a single, standard framework bundle.
    Alternatively, if your code was sufficiently modular, you could create
    multiple frameworks, but in that case, the dependencies between
    modules would be minimal or nonexistent and should not warrant the
    creation of an umbrella for them.</p>
  </blockquote>
  
  <p>Why is this approach discouraged? What makes it a good solution for Apple's problem of interdependent frameworks but not for mine?</p>