4 ms·

I don't think that's accurate. It would be like saying "Apple rejecting applications that use buttons" because the apps being rejected have buttons. I'm not say

I don't think that's accurate. It would be like saying "Apple rejecting applications that use buttons" because the apps being rejected have buttons. I'm not saying Apple is doing a good thing here, but the blog post states that it also happens for Google accounts and presumably any other web service where you'd sign up via a browser. Sending people to the site for that purpose if the service is potentially a pay one seems to be in violation of Apple's terms, though it's certainly a stretch. Apple should clarify things and not restrict browser use, but also the title is needlessly alarming.

mattmillr 14y ago
I'll agree there are much more neutral & accurate titles that could be used, but given that the title is factual (For some reason, Apple has begun enforcing a policy that they were being selective about previously, and is now indeed rejecting apps that use Dropbox.) and the source is a post to the Dropbox developer forums (not a blog post.) I don't think this title is far enough off the mark to warrant changing it. Linkbait might be "Apple still bitter Dropbox rejected buyout offer, bans API from App Store." ;)
chc 14y ago
That isn't particularly similar. The reason "Apple rejecting applications that use buttons" is a poor description is that using buttons is very, very weakly correlated to Apple rejecting your app. That isn't true here: If you use the Dropbox SDK, your app gets rejected. In fact, it's a causal relationship.