" />

Recommended: More on Avoiding App Store Rejection at Mobile Orchard


A few weeks back I recommended an article over at the excellent Mobile Orchard site, where a successful iPhone developer offered advice on how to avoid getting rejected in the App Store reviews process.  Apparently that article has drawn a large number of comments from other iPhone devs “ which have now formed the basis of a Part 2 post with lots more good tips for avoiding rejection by Apple.

Although I ‘m not a developer, I ‘ve enjoyed both these articles very much “ for the insight they give into the app reviews side of things and just for the sheer (black) humor they provide on the whole sordid and absurd (non) process.

Here are just two quick examples of the ridiculous approach that sometimes needs to be taken to get through and the marvelous inconsistency of all of it

Don ‘t Ask, Don ‘t Tell ” Sometimes being above-board doesn ‘t pay. An example: Alan Francis wrote to tell us about his experience submitting an app that included the Pinch Analytics, an package used in thousands of apps that collects anonymized usage data. As a courtesy to his users, Alan stated that he was collecting this data and provided an opt-out mechanism. Either one of these measures is unusual; combined, almost unheard of. His app was rejected until he added a giant warning label on first run, while thousands of other applications that failed to mention including analytics were allowed in.

Avoid Humor Where It ‘s Not Expected, Or Where It Violates The HIG ”
An update to the Instant New York app was rejected when its developers jokingly included the phrase ‘extra dragons ‘ in their release notes ” though, as noted by Jeff Richardson, Apple did approve an update to Google ‘s app with release notes containing ‘longer version number ‘ and ‘ninja. ‘

I used to think the technical side of being a dev was the tough part “ the actual programming skills and creativity etc. “ now I ‘m realizing that part is a doddle compared to all this nonsense.

Anyway, more great advice on navigating those murky, murky waters over at Mobile Orchard “ check out ‘Avoiding App Rejection, Part 2 ‘ HERE

Continue reading:


  • To add one from our experience, do NOT state that your update makes your app 3.0 compatible. Apple was explicit that they rejected our update to "G" because we stated it even though it was a simple fact. Lesson learned.

  • John – thanks, for me that's another great example of the sheer strangeness of all of this. I mean, hasn't Apple publicly stated that app updates *have to be* 3.0 compatible in order to get approved / that they will be reviewing on 3.0. Not exactly giving away state secrets 🙂