News

Apple changes App Store policy on private APIs

Recent reports from iPhone developers indicate that Apple has softened its stance on using private APIs—features not authorized by Apple for third-party developer use—in iPhone applications. One iPhone developer, Vimov, indicated that instead of simply rejecting its application for using private APIs, Apple approved it with a request that the developer resolve the issue in its next update. An unrelated developer, Jonah Grant reported a similar experience with his application. The iPhone SDK Developer Agreement prohibits the use of private APIs, which, unlike public APIs, may include features that Apple could change in future OS updates, and thus does not want third-party developers to use. In the past, applications that made use of private APIs have been rejected by the App Store review process, and Apple has even gone so far as to implement an automated check for the use of private APIs. The change in policy appears to be aimed at increasing approvals while educating developers about reasons for future rejection. Earlier this month Steve Jobs personally intervened to reverse the rejection of the Knocking application, which also made use of a private API. (via AppleInsider and Daring Fireball).

Comments

1

I just wish they’d allow 3rd party access to the alarms that have been set with the native Alarm Clock app. As it is, if you’re using a 3rd party app and it isn’t running, no alarms—if you could at least view (not necessarily edit, though that would be nice) internal alarms with a 3rd party app, that’d be great!