I agree there are quite a few problematic areas of this article (It reads like a advertisement for the author's app to me also), but a few of the negatives he l

I agree there are quite a few problematic areas of this article (It reads like a advertisement for the author's app to me also), but a few of the negatives he listed are issues I've encountered in my career in iOS Development, albeit a career much shorter than yours. > Provisioning Profiles Provisioning profiles are still an annoyance if using tools such as Jenkins to compile and distribute builds, as xcodebuild has to be used to build the app. This forces you to manually set up the profiles and consequently run into many of the problems that have been solved with automatic signing. This also affects ad-hoc deployment as the process of adding new testing devices requires the generation and download of a new ad-hoc provisioning profile onto the Jenkins machine. >Without the author listing the reasons for rejections it's hard to draw a conclusion here but complaints about rejections are usually BS. I don't think this is the case of all apps. In the past few months my company has easily over ten rejections, due to the fact that our app targets a niche that the reviewers are not knowledgeable on. For instance, we received two rejections in the last month over the wording of our background location services requests. We use industry specific keywords that reviewers did not know, but users of our apps most definitely would know. It is true that these issues are generally sorted out easily, but we still receive rejections and it can get frustrating. Regardless, the author stated he received 7 rejections before being approved. It seems to me that if the author's app was rejected this many times, he failed to follow Apple's app review guidelines in some form (Complete conjecture of course).