4 ms·
If the developer explain it nicely will probably get the app approved as it is a “reader” app, therefore exempt from some restrictions. So the corporate policy
by stcredzero 6y ago
If the developer explain it nicely will probably get the app approved as it is a “reader” app, therefore exempt from some restrictions.
So the corporate policy is that they'll reject, with a low level of comprehension, and if the developers don't bother to explain, too bad.
From the POV of the reviewer, they benefit from greater throughput, so just low-comprehension reject, and deal with the clarification.
Apple thinks of itself as some kind of advanced, disruptive, with-it company. The way it acts, is sometimes more like an atherosclerotic bureaucracy.
- mrtksn 6y agoI don’t know if that’s the policy or the reviewer simply screwed up but if the developer doesn’t bother to explain, yeah, too bad. Let’s not pretend that explaining what your app does is a huge burden that only few can overcome. You sign a business deal with Apple to distribute your app, you are expected to do your part. If you think that this is something you rather don’t do, then don’t work with Apple. I don’t think that having to explain how your app works is a unfair burden in the business.
- stcredzero 6y agoLet’s not pretend that explaining what your app does is a huge burden that only few can overcome. Let's not pretend that convenient nonsensical seeming rejections, which contradict common sense, and seem to imply a hostile demand of censorship are really an acceptable way of communicating in business.