Our app got rejected again. We're trying to figure out why.
graffitigeo.posterous.com
Our app got rejected again. We're trying to figure out why.
1–10 of 28 posts
Re: Our app got rejected again. We're trying to figure out why.
#2It seems like the comments you posted from Apple explain pretty clearly why, but according to the App Store, it looks like it's for sale - or isn't it?
Re: Our app got rejected again. We're trying to figure out why.
#3It seems like the comments you posted from Apple explain pretty clearly why, but according to the App Store, it looks like it's for sale - or isn't it?
We have no references to "beta" or "demo" in our metadata, binary, or application. So I'm not sure what they are referring to there. The "feature limited" part is confusing to us--we're not actually sure if they are referring to the mobs functionality or not.
The current version in the App Store is 1.0, we've since posted 1.1 and are nearing a completion of 1.2 ;) Perhaps we just skip 1.1 by the time this gets approved.
Re: Our app got rejected again. We're trying to figure out why.
#4All of these things can be handled once, together, in a single e-mail.
Actually for app reviewing throughput purposes, disqualifying the app on the first major thing they catch is a good idea on Apple's part.
Re: Our app got rejected again. We're trying to figure out why.
#5"Companies succeed with single founders all the time. Just look at Digg, Craigslist, eBay, Netflix, Wordpress, Wikipedia, Amazon, TechMeme, PBWiki, TechCrunch, TechMeme, and Etsy."
Again repetition in short published list. Am I going insane? Do you also see this?
Re: Our app got rejected again. We're trying to figure out why.
#6All of these things can be handled once, together, in a single e-mail. Actually for app reviewing throughput purposes, disqualifying the app on the first major thing they catch is a good idea on Apple's part.
Maybe it saves time on the reviewer's part, but increases developer frustration. Which is more valuable to Apple?
Re: Our app got rejected again. We're trying to figure out why.
#7All of these things can be handled once, together, in a single e-mail. Actually for app reviewing throughput purposes, disqualifying the app on the first major thing they catch is a good idea on Apple's part.
Maybe it saves time on the reviewer's part, but increases developer frustration. Which is more valuable to Apple?
I'd say that complaint pales in comparison to things like the seemingly inconsistent application of the guidelines and lack of feedback so I think they're absolutely correct to err on the side of getting more apps through the pipeline in that case.
Re: Our app got rejected again. We're trying to figure out why.
#8All of these things can be handled once, together, in a single e-mail. Actually for app reviewing throughput purposes, disqualifying the app on the first major thing they catch is a good idea on Apple's part.
It depends on whether or not the application is resubmitted. If, after the first rejection the developer says "to hell with this" and never comes back then the throughput is increased. However, if the developer subsequently resubmits only to be tripped up on the next item then you've increased the overhead for both the developer and Apple. Each resubmission is more overhead.
Re: Our app got rejected again. We're trying to figure out why.
#9"Companies succeed with single founders all the time. Just look at Digg, Craigslist, eBay, Netflix, Wordpress, Wikipedia, Amazon, TechMeme, PBWiki, TechCrunch, TechMeme, and Etsy." Again repetition in short published list. Am I going insane? Do you also see this?
You're in the wrong thread.
Re: Our app got rejected again. We're trying to figure out why.
#10We have also received ambiguous feedback from an Apple developer program reviewer. With the 2+ weeks waiting period in the queue, developers deserve more detailed responses so they are not waiting with no clue if their next binary submission will appease the inconsistent reviewers.