title: What exactly is a Private API, and why will Apple reject an iOS App if one is used?
body: <p>I've read several articles about this, and I just want to see if I understand this correctly:</p>
  
  <p>Apple will reject your app if you use a Private API...</p>
  
  <ol>
  <li><p>What is the main difference between a "Private API" and a "Non-private API?"</p></li>
  <li><p>Are the "Non-private" APIs only the APIs provided and verified by Apple?</p></li>
  <li><p>Isn't an API just a way of interacting with a Framework, and a Framework is just a set of encapsulated classes/headers that people can use for trivial purposes?</p></li>
  <li><p>Wouldn't this mean that I cannot reuse anyone's code (other than Apple's) at all in my app?</p></li>
  <li><p>If this is true, whenever a programmer makes his or her own custom classes and methods, isn't he technically designing a mini Framework just for his specific purpose? So wouldn't this mean that he is using his own private API?</p></li>
  <li><p>What would even be the difference between using someone else's classes/methods alongside my classes/methods, how could they even tell the difference, and why would this be a problem?</p></li>
  </ol>
  
  <p>My understanding of this sounds absurd, and don't believe I am understanding what a "Private API" is correctly. I did read that it was to protect against any changes in the API that could render your App dysfunctional. Does this mean APIs are linked during run time (as opposed to compile time) and can be updated automatically without you knowing or something? (See, I was originally thinking of APIs/frameworks as being set in stone whenever you compile, maybe this is where I am wrong)</p>
  
  <p>Can someone please help me out? I'm really confused about this policy. Thank you!</p>