Linked by Thom Holwerda on Mon 16th Nov 2009 19:48 UTC
Apple "Continued issues with the App Store approval process are prompting developers to shun the platform entirely. Though there are tens of thousands of other developers pumping out over 100000 iPhone apps, will continued migration away from iPhone development result in less quality software for the platform? Worse yet, will users even care?"
Permalink for comment 395082
To read all comments associated with this story, please click here.
RE: private API?
by Chicken Blood on Tue 17th Nov 2009 18:25 UTC in reply to "private API?"
Chicken Blood
Member since:
2005-12-21

So whats so private about the API? Why have an API you can't use? He has been using it for some time so it obviously isn't changing. Does it do something not able to be done by another means?


Private APIs are usually undocumented and not externally exposed in a header. You have to examine the object code to know that they are there.
They are written for internal use by the library vendor and often address a specific issue or use case from within. There may be an intention to eventually make them public, but the behavior and API has not been fully vetted for them to be considered fit for public consumption. They are inherently unstable because the function signature, its implementation (or the fact that it exists at all) can change from one dot release to the next. Using a private API, runs the risk of your app suddenly crashing or behaving unexpectedly. The fact that in this case, the API had not changed (yet) is irrelevant.

Other issues aside, anyone using private APIs in their app should not be surprised if it is rejected from the app store.

Reply Parent Score: 2