Comments on: Three20 Framework and More on App Store Screening for Private APIs http://www.imore.com/2009/11/20/three20-framework-app-store-screening-private-apis/ More of everything iPhone and iPad Sat, 26 May 2012 06:24:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: dev http://www.imore.com/2009/11/20/three20-framework-app-store-screening-private-apis/comment-page-1/#comment-95482 dev Sat, 21 Nov 2009 05:34:01 +0000 http://www.theiphoneblog.com/?p=15459#comment-95482 <p>On the other hand, Hewitt tweeted a couple of interesting points -- that apps like Quad Camera and the entire category that has become augemented reality apps would not exist if developers had not (ab)used private APIs to push the state of what is allowed on the App Store.</p> On the other hand, Hewitt tweeted a couple of interesting points -- that apps like Quad Camera and the entire category that has become augemented reality apps would not exist if developers had not (ab)used private APIs to push the state of what is allowed on the App Store.

]]> By: dev http://www.imore.com/2009/11/20/three20-framework-app-store-screening-private-apis/comment-page-1/#comment-95407 dev Fri, 20 Nov 2009 20:06:29 +0000 http://www.theiphoneblog.com/?p=15459#comment-95407 <p>Setting aside the problem of false positives -- something for which anybody who has dabbled in code can appreciate -- RogueSheep's summary claims the rejection came "halfway" through the review process. Even if you buy the questionable game theory-ish argument about keeping developers in the dark, why so long?</p> <p>Since the static analysis tool is automated and (guess) just peeks through the symbol table in the binary app, why on Earth would Apple not just run this through when the binary is uploaded, and give the developer an immediate warning/list of flagged questionable calls, that they developer could work on while the rest of the review proceeds? It would seem faster for the developers, faster for Apple, and less labor all around.</p> Setting aside the problem of false positives -- something for which anybody who has dabbled in code can appreciate -- RogueSheep's summary claims the rejection came "halfway" through the review process. Even if you buy the questionable game theory-ish argument about keeping developers in the dark, why so long?

Since the static analysis tool is automated and (guess) just peeks through the symbol table in the binary app, why on Earth would Apple not just run this through when the binary is uploaded, and give the developer an immediate warning/list of flagged questionable calls, that they developer could work on while the rest of the review proceeds? It would seem faster for the developers, faster for Apple, and less labor all around.

]]> By: jake http://www.imore.com/2009/11/20/three20-framework-app-store-screening-private-apis/comment-page-1/#comment-95396 jake Fri, 20 Nov 2009 18:47:15 +0000 http://www.theiphoneblog.com/?p=15459#comment-95396 <p>kewl</p> kewl

]]>