3 ms·
Well, they were told it's because they were using private frameworks. Which means not-locked-down APIs. That's just inviting them to be yanked at some point,
by Groxx 17y ago
Well, they were told it's because they were using private frameworks. Which means not-locked-down APIs. That's just inviting them to be yanked at some point, as they're just waiting to break. Frankly, it's surprising they got through at all, Apple was being rather loose with their rules in this area.
Plus, they're duplicating functionality, which they've been rather explicit in the past about not allowing.
- morisy 17y agoNot approving apps that are going to break because they use private frameworks makes sense, but pulling a wide variety in one genre after they've been published and found a foothold just sucks. And while Apple has been "explicit" about not allowing "duplicate" functionality, that standard is incredibly vague in practice and incredibly arbitrary in enforcement. In this case, one of what I presume is the banned apps (the article doesn't mention any, grr!) supported some non-duplicative features for war driving assistance, as well as a "radar" view. So yes, some features are duplicated, just like Pandora duplicates some features (playing, pausing music) that iTunes does. WiFiFoFum's product review/description page on MacWorld, with 1,549 reviews: http://bit.ly/bF4gMP http://bit.ly/bF4gMP
- Groxx 17y agoSucks, yes, I'm not defending the suckiness of the app store. Few can deny that. But its purpose is not to lower suckiness for developers, it's to lower suckiness for consumers. They're merely being consistent in that goal.