I haven't heard of anyone's pre-approved apps getting pulled for being
brought to their attention when trying to get another one through - so
you're probably fine to mention that to them - but ... I also doubt it
will work.
You need to convince them that this is more than what it appears to be
- it *looks* like a simple app that any developer could write as "my
first app". If it's more than that, make it more obvious. Sometimes
stupid changes are enough - with the Ker-Ching app (a sound effect
that goes "ker-ching"), the developer only had to add something tiny
to get approved. Cant remember what, but it was something trivial,
like "a count of the number of times you've hit kerching".
Maybe do something more with the cloud? I recommend something "visual"
- they tend to notice it that way :).
> --
> You received this message because you are subscribed to the Google Groups
> "Brighton iPhone Creators" group.
> To post to this group, send email to
> brighton-iph...@googlegroups.com.
> To unsubscribe from this group, send email to
> brighton-iphone-cr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/brighton-iphone-creators?hl=en.
If you go for appeal, they will in certain cases tell you what you need to change, we did, made the changes and it went through review.
Warning though, the appeal process will likely take 3+ weeks.
So the question is: is it quicker to make changes, submit and wait for review, or go for appeal and wait to see what changes you've got to make to then submit wait etc.
My gut instinct is that if they are saying the app is too simple - irrespective of what they have let through previously - you need to make changes as per Adam's advice.
(NB. the issue for the app we had submitted was for something I'd done, submitted and successfully got into the app store previously)
Adam is right you need to show that it's not just rendering content that could easily be done as just a web app
As for the same person reviewing your apps, it's unlikely. And even if they had they see so many each day I'd be surprised if they can remember one from the other
I've had apps approved, only to be rejected at the next update because the reviewer had noticed something in the app description they didn't like even though it was there in the original submission
We have had some mixed results, first with Modern Toss when we successfully appealed with our Daily Toss app and then failed in appealing for Periodic Table of Swearing. Another book sampling app for a big UK trade published failed for "lack of entertainment value" - we never got to the bottom of whether the publisher appealed properly or not.
It is just part of the game - they are a shop that looks after its customers and they make the call. They might be wrong but we can go elsewhere.
Adrian
Aimer Media
It is worth additionally noting that they will reject some type of apps if they are in a popular area - tech news might fall into that category. They are also tending to move against cookie-cutter apps - some of the dictionary and travel publishers are being told to create container apps and not specific app per category.
We have had some mixed results, first with Modern Toss when we successfully appealed with our Daily Toss app and then failed in appealing for Periodic Table of Swearing. Another book sampling app for a big UK trade published failed for "lack of entertainment value" - we never got to the bottom of whether the publisher appealed properly or not.
It is just part of the game - they are a shop that looks after its customers and they make the call. They might be wrong but we can go elsewhere.
Adrian
Aimer Media
On 11 Apr 2012, at 20:37, Adam Martin wrote:
Bob
Ps I just got rejected for leaving a redundant info.plist in the bundle that was not even being used by the app :(
Sent from my iPad