4 ms·

With billions of cash in the coffers (albeit a substantial portion of it, offshore and quite tricky to bring it home without losing a chunk in taxes) could Appl

With billions of cash in the coffers (albeit a substantial portion of it, offshore and quite tricky to bring it home without losing a chunk in taxes) could Apple not afford to offer non-curt remarks as to why a certain app was rejected; perhaps throw a bone to the developer in the form of suggestions and comments as to what was lacking or what was overdone? If the Apple legal team had indeed convinced Tim Cook et al. that including remarks and suggestions with app rejections would be tantamount to inviting a lawsuit frenzy, then Apple had truly lost gumption and chutzpah since Jobs left the reins. Often it is not the rejection itself that stings but the manner in which it is 'dispatched'.

k-mcgrady 13y ago
>> "If the Apple legal team had indeed convinced Tim Cook et al. that including remarks and suggestions with app rejections would be tantamount to inviting a lawsuit frenzy, then Apple had truly lost gumption and chutzpah since Jobs left the reins." Seriously, the Jobs thing again? Rejection worked the same when he was in charge. In fact it was worse. Communication through things like the Resolution Center has much improved in the last couple of years.
mikeho1999 13y ago
As someone who has had a number of rejections from Apple (most of which have been corrected and thereafter accepted), I disagree with the comment. Every time I have gotten a rejection, I have been pointed directly to the app store guidelines the specific bullet point or line item(s) as the reason for the rejection. Most of the time, reading thru those bullet points were enough for me to figure out the "error" in my ways (although, some may argue that the guidelines themselves may be a bit draconian, but that's definitely a topic for another conversation...), and I was able to make the proper corrections, resubmit, and it was accepted. Only on two occasions, was that not enough -- one time I disagreed with their assessment, and on the other time, I was confused as to how the guideline applied. Both times I submitted an appeal, and both times I received a response from an actual person / case manager who explained in much more detail what was going on. (Now, whether or not the responses were timely is another issue... but I again, I digress...) So, at least from my experience (3+ years of iOS development now), I haven't seen any cases where an app I was working on was rejected, without enough information to make the necessary corrections to fix the problem. Sure, it'd be nice and incredibility useful to the innovation curve if the information was dispatched a more time efficient manner... but to say that the information was "lacking" and "curt" just hasn't been the case, at least for me and my experience.

k-mcgrady 13y ago

>> "If the Apple legal team had indeed convinced Tim Cook et al. that including remarks and suggestions with app rejections would be tantamount to inviting a lawsuit frenzy, then Apple had truly lost gumption and chutzpah since Jobs left the reins." Seriously, the Jobs thing again? Rejection worked the same when he was in charge. In fact it was worse. Communication through things like the Resolution Center has much improved in the last couple of years.

mikeho1999 13y ago

As someone who has had a number of rejections from Apple (most of which have been corrected and thereafter accepted), I disagree with the comment. Every time I have gotten a rejection, I have been pointed directly to the app store guidelines the specific bullet point or line item(s) as the reason for the rejection. Most of the time, reading thru those bullet points were enough for me to figure out the "error" in my ways (although, some may argue that the guidelines themselves may be a bit draconian, but that's definitely a topic for another conversation...), and I was able to make the proper corrections, resubmit, and it was accepted. Only on two occasions, was that not enough -- one time I disagreed with their assessment, and on the other time, I was confused as to how the guideline applied. Both times I submitted an appeal, and both times I received a response from an actual person / case manager who explained in much more detail what was going on. (Now, whether or not the responses were timely is another issue... but I again, I digress...) So, at least from my experience (3+ years of iOS development now), I haven't seen any cases where an app I was working on was rejected, without enough information to make the necessary corrections to fix the problem. Sure, it'd be nice and incredibility useful to the innovation curve if the information was dispatched a more time efficient manner... but to say that the information was "lacking" and "curt" just hasn't been the case, at least for me and my experience.