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?"
Thread beginning with comment 395047
To read all comments associated with this story, please click here.
private API?
by TechGeek on Tue 17th Nov 2009 16:10 UTC
TechGeek
Member since:
2006-01-14

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?

I don't buy that Apple is trying to control the user experience. If that were the case, they would only accept the best of apps or maybe the top X%, The rest would be rejected. But thats not the case. How many flashlight apps are there on the app store? How many do you really need? Plus, how do you justify asking a company to spend money on development when they have no guarantee that their app will even make it into the store?

Reply Score: 3

RE: private API?
by Chicken Blood on Tue 17th Nov 2009 18:25 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

RE[2]: private API?
by memson on Tue 17th Nov 2009 22:16 in reply to "RE: private API?"
memson Member since:
2006-01-01

Plus Apple has been pretty laid back about this up till now - even though it is expressly against the Developer Agreement to use them. They just started static analysis of the submitted apps, so they are now picking up on this stuff. Why static analysis? They'll also pick up other less nice stuff, such as "naughty" things people are trying to mask or potential security risks.

Reply Parent Score: 2