First, to preface: Believe it or not, I am far from an Apple fanboy. I have never owned an iPhone, Apple Watch, Mac, or MacBook for personal use. I have owned o

First, to preface: Believe it or not, I am far from an Apple fanboy. I have never owned an iPhone, Apple Watch, Mac, or MacBook for personal use. I have owned one iPad, which I bought a few years ago. I also like the AirPods. I like (and dislike) a lot of things about Apple's DX, and I dislike (and like) a lot of things about their UX. That said, I agree, lack of consistency is frustrating. But there is a big caveat to that opinion. When I experience inconsistent rejection, it has always been due to things that are reasonable to not catch as a reviewer 100% of the time. But personally, I would rather they catch 75% of instances of a problem than give up and let them all through because the inconsistency is frustrating. Of course, I would really like them to get that number to 100%, but I acknowledge that a lot of this stuff is not easily captured at a 100% rate using a tester script, or automatic processing. The key here is of course that you agree with or understand the rule they are enforcing. This is probably where most of the disagreement actually lies, and not so much in the inconsistency. I happen to be the kind of "purist" who would rather things be stricter for developers. I want the UX to be as good as possible, and I want the APIs to continue to improve and to not burden/complicate the platform with a lot of backwards compatibility. This is the opposite of a lot of developers, and I totally understand the other side of that argument. This is not to say that Apple review is not shitty sometimes. I just happen to think that the one or two biggest things developers complain about seem to not be as clear-cut as developers describe.