3 ms·
> I've been developing on iOS since about 6 months after the App Store became a thing. I've developer dozens of apps and submitted hundreds of updates. I can co
by kbenson 9y ago
> I've been developing on iOS since about 6 months after the App Store became a thing. I've developer dozens of apps and submitted hundreds of updates. I can count on my fingers the number of rejections I've got and there were only one or two that were 'silly' (and those were fixed through a quick appeal).
So,you've pretty much established yourself as an expert in the ecosystem. That actually lends less credence to your counterarguments in my eyes. It's all too easy as an expert to overlook the pain points that you've become accustomed to, or did not notice as they were slowly layered up over the years. In my experience, the expert that rages against the system they use is far more likely to have valid input than the expert that apologizes for it.
That's not to say you're wrong. Just that in my eyes the likelyhood of you being right dropped as you explained how much experience you had (past a certain threshold. Amateurs often don't understand enough to accurately critique as well).
- k-mcgrady 9y agoI understand your point but I think length of time developing for the platform (in this specific example) is important. Based on my experience (and I'm willing to bet if there is a large set of data available on rejections it would back me up) 7 rejections is extreme leading me to believe something is up on the authors end, not Apple's. A 5 min glance at the App Store guidelines will prevent 99% of rejections. Skill doesn't really come into avoiding rejections (besides bugs in your code of course).
- cptskippy 9y agoThe guidelines are very nuanced and reviewers are free to interpret them as they see fit. We have had an app in the store for over 2 years that jumped through hoops to avoid the 30% Apple Tax to accept a charitable donation in app. Our Apple account Rep reached out to our marketing director in the fall of last year to tell us the policy changed and that we wouldn't have to do stupid shit anymore. So we spent Nov and December developing a much improved experience. It was submitted, approved and has been available in the store since before Christmas. This week we received notification that our app violated the guidelines with regards to that specific feature and we had 2 weeks to fix it.
- coldtea 9y ago>It's all too easy as an expert to overlook the pain points that you've become accustomed to, or did not notice as they were slowly layered up over the years. Same holds for the inverse: it's easy as a newb to consider everything as a pain point, even if it's a well designed procedure.
- kbenson 9y ago> Same holds for the inverse: it's easy as a newb to consider everything as a pain point, even if it's a well designed procedure. Sure, that's why I noted as much with my last sentence. :)
- inputcoffee 9y agoI wish we could find the Goldilocks developer to render a verdict. Someone who has just enough experience to not be used to it, but not so little that they haven't learned to use it.
- afarrell 9y agoAsk someone with experience who then became a teacher and re-familiarized themselves with the pain points.
- hinkley 9y agoMan, you just described my day job. And the last contract I worked.
- FussyZeus 9y agoSpeaking as another "expert" I guess, honestly it's pretty hard to get a rejection. Almost all of mine are due to an oversight with things like the app's data and permissions, or relating to the app age rating. Seriously if your app gets rejected that much that you'd bitch about it, it's because you're not paying attention to what you're doing and/or are up to some shady shit. It's really not difficult to avoid.
- valuearb 9y agoI've been rejected more than anyone on a per app basis, and your 100% right. Almost all rejections were foreseeable from reading the guidelines, in many cases I just wanted to test the boundary.