title: Why are build types distinct from product flavors?
body: <p><em>Preface: this is not a question about how to use build types and product flavors in an Android app. I understand the basic concepts involved. This question is more about trying to understand which configuration should be specified in a build type, which configuration should be specified in a product flavor, and whether any distinction is actually necessary.</em></p>
  
  <p>This week, I've been learning more about gradle configuration for Android apps. I initially thought I had a good handle on build types vs product flavors, but the deeper I got into the documentation the more I realized the distinction between the two was not clear to me at all.</p>
  
  <p>Since there is a well-defined hierarchy (in the sense that properties specified in build types take precedence over those specified in product flavors), I don't understand why there is a need to distinguish between build types and product flavors at all. Would it not be better to merge all properties and methods into the product flavor DSL object, and then just treat build type as a (default) flavor dimension?</p>
  
  <p>Some concrete examples that led to my confusion:</p>
  
  <ul>
  <li><p>The <code>signingConfig</code> property can be set in both build types and product flavors... but <code>minifyEnabled</code> (and, I assume, <code>shrinkResources</code>?) can only be configured in build types.</p></li>
  <li><p><code>applicationId</code> can only be specified in product flavors... and <code>applicationIdSuffix</code> can only be specified in build types!?</p></li>
  </ul>
  
  <p><strong>The actual question(s)</strong>:</p>
  
  <p>Given the above examples: is there a clear distinction between the roles of build types vs product flavors?</p>
  
  <p>If so, what is the best way to understand it?</p>
  
  <p>If not, is the plan to eventually merge build types and product flavors into a single configurable DSL object?</p>