Most iPhone users have no idea what an API is, let alone the difference between a public and a private one. But developers know that an application programming interface is not only important to how a smartphone app interacts with other software, but whether it will make the cut into the all-important, exponentially growing Apple App Store.
As recently as last month Apple was aggressively weeding out apps that use a private API because they can cause compatibility problems. The Apple licensing agreement specifically notes that using a non-documented API is a violation of its terms.
Now, there seems to be a crack in the armor. First came word that a Google app for the iPhone was allowed into the inventory with a private API. Now Apple has apparently approved a much smaller developer, Vimov, maker of iSimulate, with just a warning.
AppleInsider reported Friday that Apple’s memo to Vimov states only that “Applications may only use documented APIs in the manner prescribed by Apple and must not use or call any private APIs. While your application has not been rejected, it would be appropriate to resolve this issue in your next update.”
iSimulate duplicates some features of the iPhone in a simulator for Mac computers.
If an API is private, or unpublished, it raises concerns that it will not be updated quickly enough to keep up with new operating systems. Public APIs allow developers to keep up to date with changes.
The iPhoneblog reported earlier this month that Apple was using static analysis tools to detect private APIs.
Apple has also cited security reasons for blocking private APIs, dumping games made by Unity out of concern that the APIs could be collecting personal information.
But when Google released its mobile application with voice search, enterprising analysts found that there was no public API for…