I don't agree that a talented indie developer can't build an immersive, beautiful iPad app. The problem is that it's not worth the risk of investing the time to build it only to get rejected by Apple. Mac apps do not have this problem.
Maybe the only way to mitigate the risk of the capricious app store gatekeepers is to build enough relationships with Apple to bypass them (like ngmoco seems to do). Maybe that requires being a big(ger) company.
Rejections (by which I mean - "we are not putting this on our store") are an imaginary issue. They are so few and far between that you'd be hard pressed to find a developer who had had an app rejected. Also in my experience the "app store gatekeepers" have been far from capricious and in fact rather sensible. And unlike less than a year ago, now Apple are proactive in communicating with developers - detailed information what issues they've found (including things like screenshots and even suggestions how the issue can be solved), follow up ID, contact information (including phone) of a person that can answer any further questions you might have, etc.
In short, if you are reasonable (e.g. not trying to sneak in a porn app or an app that obviously violates Apple's terms) you are practically guaranteed that you'll get your app in the store. And if you are not reasonable being big or close to Apple will likely not help you much.
(By the way, I cannot come up with a single case in which ngmoco might seem to have bypassed the approval process. Do they have a tits app in the store or something?)
After 6 months of suggestions to one of my clients, they retroactively decided to flat out forbid 2 party phone call recording apps from the store.
He was flat out rejected. After being suggested to put in-app purchasing in his app.
I'd say "App store reviewers are tired, cranky, varied from one another, pissed off when people dump crap on them, and unwilling to go out on a limb when in doubt", and that accounts for 90% of all the rejections and behavior we see from them.
Phone call recording gets into dicey legal ground. I'm aware that 2 party covers most of the situations but it's mess they likely don't want to deal with.
Phone call recording with notification is very legal. We could very easily call the second party on the call and play a message before combining the calls that clearly points out the call is being recorded
Either way, they're not liable in the slightest for it.
All of that aside, it doesn't really matter. If you don't want to get into a call recording app, you say that at the beginning when first shown a call recording app. After you've suggested a company do 10k worth of development, then make a policy rejection on something the app has done since day one, you've screwed up.
So preventing the sell of a useful tool that might or might not be used legally while under the control of someone who is informed of the distinction and able to take that responsibility themselves.... how paternal of them.
I hardly see it as a rarity. The majority of app developers I know (myself included) have had apps rejected. It isn't just porn these days - it is language that apple views as derogatory, things that apple views as solicitation, etc.
I do commercial iPhone (and now iPad) development for a living.
You can make immersive beautiful apps. But you have to go about it the right way.
Apple only approves working code. This means you have to get iterative in the correct way to 1> Lessen your chance of late rejection and 2> Ensure you have approval the entire way.
If you're making an app, make a simple version of it first. Submit it for approval, after approval or rejection, fix those problems it has, then resubmit. Iterate this. Only when you've got a pretty much done project, buy the art, add it in, then resubmit.
There are apple development liaisons who you can develop a relationship with, but honestly, they'll call you even if you don't have one when they think your app is in the "sweet spot" of "rejected by approvable with just a little tweak". The relationship is pretty much only useful to "get" their mindset faster, it doesn't really get more things approved.
Is there a risk they'll end up rejecting you wholesale? Yup. But it's pretty reasonable to get a feel for what areas are verboten, and which areas are largely in the clear. Stay in the latter, and you're usually far far from fearing rejection.
Comments
I don't agree that a talented indie developer can't build an immersive, beautiful iPad app. The problem is that it's not worth the risk of investing the time to build it only to get rejected by Apple. Mac apps do not have this problem.
Maybe the only way to mitigate the risk of the capricious app store gatekeepers is to build enough relationships with Apple to bypass them (like ngmoco seems to do). Maybe that requires being a big(ger) company.
Rejections (by which I mean - "we are not putting this on our store") are an imaginary issue. They are so few and far between that you'd be hard pressed to find a developer who had had an app rejected. Also in my experience the "app store gatekeepers" have been far from capricious and in fact rather sensible. And unlike less than a year ago, now Apple are proactive in communicating with developers - detailed information what issues they've found (including things like screenshots and even suggestions how the issue can be solved), follow up ID, contact information (including phone) of a person that can answer any further questions you might have, etc.
In short, if you are reasonable (e.g. not trying to sneak in a porn app or an app that obviously violates Apple's terms) you are practically guaranteed that you'll get your app in the store. And if you are not reasonable being big or close to Apple will likely not help you much.
(By the way, I cannot come up with a single case in which ngmoco might seem to have bypassed the approval process. Do they have a tits app in the store or something?)
After 6 months of suggestions to one of my clients, they retroactively decided to flat out forbid 2 party phone call recording apps from the store.
He was flat out rejected. After being suggested to put in-app purchasing in his app.
I'd say "App store reviewers are tired, cranky, varied from one another, pissed off when people dump crap on them, and unwilling to go out on a limb when in doubt", and that accounts for 90% of all the rejections and behavior we see from them.
Phone call recording gets into dicey legal ground. I'm aware that 2 party covers most of the situations but it's mess they likely don't want to deal with.
Phone call recording with notification is very legal. We could very easily call the second party on the call and play a message before combining the calls that clearly points out the call is being recorded
Either way, they're not liable in the slightest for it.
All of that aside, it doesn't really matter. If you don't want to get into a call recording app, you say that at the beginning when first shown a call recording app. After you've suggested a company do 10k worth of development, then make a policy rejection on something the app has done since day one, you've screwed up.
So preventing the sell of a useful tool that might or might not be used legally while under the control of someone who is informed of the distinction and able to take that responsibility themselves.... how paternal of them.
And in what capacity is the app store legally responsibly for carrying apps that allow recording?
I hardly see it as a rarity. The majority of app developers I know (myself included) have had apps rejected. It isn't just porn these days - it is language that apple views as derogatory, things that apple views as solicitation, etc.
I do commercial iPhone (and now iPad) development for a living.
You can make immersive beautiful apps. But you have to go about it the right way.
Apple only approves working code. This means you have to get iterative in the correct way to 1> Lessen your chance of late rejection and 2> Ensure you have approval the entire way.
If you're making an app, make a simple version of it first. Submit it for approval, after approval or rejection, fix those problems it has, then resubmit. Iterate this. Only when you've got a pretty much done project, buy the art, add it in, then resubmit.
There are apple development liaisons who you can develop a relationship with, but honestly, they'll call you even if you don't have one when they think your app is in the "sweet spot" of "rejected by approvable with just a little tweak". The relationship is pretty much only useful to "get" their mindset faster, it doesn't really get more things approved.
Is there a risk they'll end up rejecting you wholesale? Yup. But it's pretty reasonable to get a feel for what areas are verboten, and which areas are largely in the clear. Stay in the latter, and you're usually far far from fearing rejection.