4 ms·

This is true. My only bug with apple right now is the lack of transparency in the App Store Submission Process. The rest is really their decision, the hacking c

This is true. My only bug with apple right now is the lack of transparency in the App Store Submission Process. The rest is really their decision, the hacking community is relatively free to do what they want, and apple knows it's good for them.

invisible 16y ago
While I tend to agree, deciding whether an app will probably get allowed in doesn't take serious brain power. Does it duplicate something that Apple spends tons of R&D money on (e.g. phone capabilities, "redoing" what the iPhone normally does, etc)? Probably avoid stepping on too many toes. Do you use private APIs? I'd rewrite. Is it illicit? Good luck on that one.
- chc 16y ago
  You forgot these actual reasons apps have been rejected: - Is it a picture frame? - Does it include political cartoons? - Does it include an ideograph of a clock? - Does it do the exact same thing as the previous version, which was accepted? - Does it include legally licensed song lyrics that mention sex (with the appropriate "adult content" black mark)? - Does it display an unoffensive screenshot from a Mac? - Does it allow access to the Internet through public APIs? - Does it mention the price of the Voyager spacecraft? - Does it use the extremely popular OpenFeint network and the reviewer happens to be in a bad mood that day?
  - invisible 16y ago
    I have never seen 1/3 of those reasons and I'd wager there is more to the story than is let on. The problem is you see a developer crying foul when we have no idea - and the app may go on to be "fixed" and then approved. Just because someone writes a blog post as soon as they freak out about being rejected doesn't mean they're correct.
    - chc 16y ago
      I'm sure you have never seen 1/3 of those reasons. That was my point — Apple can and does reject apps for any completely unpredictable, off-the-wall reasons. It's not nearly as cut-and-dried as you made it sound. Also, can you give an example of a major rejection story where the developer "freaked out about being rejected" and wasn't right? I don't think that happens. Apple usually tells you in no uncertain terms when your submission has been rejected. And yes, the app may go on to be "fixed" and then approved, or it might not. That doesn't change the fact that it was rejected for a bizarre reason to begin with, in contradiction of your claim that only apps that use private APIs and illegal and confusing apps get turned down. There are many more reasons, a lot of which aren't written down and a lot of which don't exist yet. That's the scariest part — Apple will just change their minds. Remember the Great Skin Purge, where they deleted tens of thousands of apps for "showing skin"?

invisible 16y ago

While I tend to agree, deciding whether an app will probably get allowed in doesn't take serious brain power. Does it duplicate something that Apple spends tons of R&D money on (e.g. phone capabilities, "redoing" what the iPhone normally does, etc)? Probably avoid stepping on too many toes. Do you use private APIs? I'd rewrite. Is it illicit? Good luck on that one.

chc 16y ago
You forgot these actual reasons apps have been rejected: - Is it a picture frame? - Does it include political cartoons? - Does it include an ideograph of a clock? - Does it do the exact same thing as the previous version, which was accepted? - Does it include legally licensed song lyrics that mention sex (with the appropriate "adult content" black mark)? - Does it display an unoffensive screenshot from a Mac? - Does it allow access to the Internet through public APIs? - Does it mention the price of the Voyager spacecraft? - Does it use the extremely popular OpenFeint network and the reviewer happens to be in a bad mood that day?
- invisible 16y ago
  I have never seen 1/3 of those reasons and I'd wager there is more to the story than is let on. The problem is you see a developer crying foul when we have no idea - and the app may go on to be "fixed" and then approved. Just because someone writes a blog post as soon as they freak out about being rejected doesn't mean they're correct.
  - chc 16y ago
    I'm sure you have never seen 1/3 of those reasons. That was my point — Apple can and does reject apps for any completely unpredictable, off-the-wall reasons. It's not nearly as cut-and-dried as you made it sound. Also, can you give an example of a major rejection story where the developer "freaked out about being rejected" and wasn't right? I don't think that happens. Apple usually tells you in no uncertain terms when your submission has been rejected. And yes, the app may go on to be "fixed" and then approved, or it might not. That doesn't change the fact that it was rejected for a bizarre reason to begin with, in contradiction of your claim that only apps that use private APIs and illegal and confusing apps get turned down. There are many more reasons, a lot of which aren't written down and a lot of which don't exist yet. That's the scariest part — Apple will just change their minds. Remember the Great Skin Purge, where they deleted tens of thousands of apps for "showing skin"?