Hacker News new | ask | show | jobs
by kall 1484 days ago
Google would just tell you that your app metadata does not comply with the Play Store terms of service and let you figure it out by trial and error.
1 comments

I mean you say that, but having done about ~60 releases for the same app on both platforms over the last three years, google has only once caused us an issue (due to changes in privacy policy disclosure requirements that we had to rectify), whereas Apple has prevented us from deploying at least a dozen times over the same period, several times for issues that they hadn't flagged in previous releases, and sometimes having us wait for up to 2 days for re-review.
I guess it's a matter of anecdotes. I certainly don't have enough data (one + a half apps with countless updates) to make any serious claims. For us google has been more trouble, but I've heard other bad stories about apple too.

I'm freshly frustrated because I'm dealing with a random metadata rejection (on an "internal testing" build! nothing has changed!) just now.

The anecdotal remark is fair, it may just come down to the nature of one particular type of app vs another, but on a personal note, I find things like automated metadata rejections a lot less frustrating than fickle human rejections because I can debug metadata and resubmit to receive instant feedback - akin to fighting with a compiler - whereas with apple some issues require multiple days of back and forth with reviewers while I pathologically refresh the review status page. What I find to be most frustrating is when the reviewer responds with a change request, we fix the build, then the next reviewer rejects some other random thing that wasn't mentioned in the previous review, dragging out the release date even longer. Anyway, fuck em both, cheers!