2 ms·
Definitely wearing my Apple fanboy hat here, but... > Let me give a courtesy remainder that it is "... until Apple change their mind". I'm going to propose th
by danpalmer 9y ago
Definitely wearing my Apple fanboy hat here, but...
> Let me give a courtesy remainder that it is "... until Apple change their mind".
I'm going to propose that there has been ~1 legitimate case of this in iOS history. Maybe 2?
I feel like for the most part, the original guidelines were pretty solid. While they weren't complete and have been changed significantly since the original publication, most of this has been to add guidelines around new features (like push notifications), and to clarify rules. This clarification could be read as Apple changing their mind, but I reckon almost every instance has been 'obvious' and that it would almost always be apps that were knowingly skirting way too close to the rules, and not acting within the spirit of the guidelines, that got burned.
- Tepix 9y agoI suggest you check out http://www.appstorereviewguidelineshistory.com/ http://www.appstorereviewguidelineshistory.com/ Sure, you may agree with most of them, but what if you're the developer of an app such as a cryptic watch app for the Apple Watch, and then Apple decides to block all apps on the watch who's main function is displaying the time (like they did)?
- danpalmer 9y agoThanks for the link, very useful! I would say that the cryptic watch app was 'obvious' in my mind though. Watch faces are a well defined concept on the watch, and the lack of third party watch faces was about as explicit as one can expect from Apple. I'm not surprised at all, and ignoring the fact of whether they should be allowed, I feel they were skirting too close to the boundary to be able to complain about being removed, but that's just my reading of the situation.