6 ms·

My top complaints with Apple are - The documentation could be improved a lot - with examples ideally. - The App Review process seems to flag a number of the s

My top complaints with Apple are - The documentation could be improved a lot - with examples ideally. - The App Review process seems to flag a number of the same issues which are subsequently resolved after sharing a video that there is already compliance. This could be improved - Showing specific error messages - I think this is somewhat Universal but Apple gets it wrong far more often. For example if you don't accept an Agreement somewhere in App Store Connect, you will just see a random error when you try to test In-App Purchase and some developers may think it's a problem with their code when in fact it's something else entirely. This wastes time and can be incredibly frustrating and demoralizing. Also the In-App _Purchase sandbox user flow is needlessly complicated.

diego_moita 4y ago
And also Xcode. And breaking existing functionality. But, in the end, it boils down to the fact that "developers, developers, developers" just isn't an Apple mantra (viz: Jobs' initial reluctance to open an appstore). They know that, as long as they corral a lot of paying customers the developers will keep coming, no matter how many problems they throw in the way.
pjmlp 4y ago
What about bringing back the "deprecated" documentation that is still quite relevant and only old timers like ourselves can find it, because we have the bookmarks and also know what to search for?
busymom0 4y ago
I recently went through the second one for my hacker news app HACK. I had an urgent bug fix update which fixed issues related to the hacker news website making some small html changes which broke the parsing code. Apple rejected the update saying my app didn’t allow user content to be flagged, blocked, hidden etc. this had already been dealt with in a prior update and my app already included these features. Somehow Apple reviewer decided to review the app without logging in and obviously without logging in, you won’t see the ability to flag, hide, block etc. This ended up wasting 2 days. And this is something which was already dealt with in prior update and my app already included.

diego_moita 4y ago

And also Xcode. And breaking existing functionality. But, in the end, it boils down to the fact that "developers, developers, developers" just isn't an Apple mantra (viz: Jobs' initial reluctance to open an appstore). They know that, as long as they corral a lot of paying customers the developers will keep coming, no matter how many problems they throw in the way.

pjmlp 4y ago

What about bringing back the "deprecated" documentation that is still quite relevant and only old timers like ourselves can find it, because we have the bookmarks and also know what to search for?

busymom0 4y ago

I recently went through the second one for my hacker news app HACK. I had an urgent bug fix update which fixed issues related to the hacker news website making some small html changes which broke the parsing code. Apple rejected the update saying my app didn’t allow user content to be flagged, blocked, hidden etc. this had already been dealt with in a prior update and my app already included these features. Somehow Apple reviewer decided to review the app without logging in and obviously without logging in, you won’t see the ability to flag, hide, block etc. This ended up wasting 2 days. And this is something which was already dealt with in prior update and my app already included.