I'd argue that to Apple the consumers are their stakeholders. They want to do everything in their power to make the user's experience better.
If we see Apple pulling apps of honest hard working people then I'll eat crow but in the five years of the iOS App Store how many horror stories do we have (if any)?
I will continue to give Apple the benefit of the doubt until they do something to make me question. So far I've never been inconvienced and only had a better computing experience since I got my Mac and my iPhone. That is why I, and many other people, will continue to use their products.
http://www.appleinsider.com/articles/12/01/03/ataris_legal_t... http://mashable.com/2011/12/12/apple-pulls-app/ http://www.iphonehacks.com/2012/01/process-killer-app-that-a... http://www.neoos.ch/blog/30-quickpick-pulled-from-app-store-... http://lifehacker.com/5614752/grooveshark-iphone-app-pulled-... http://www.joystiq.com/2011/12/28/imame-app-pulled-from-ios-... http://techcrunch.com/2011/12/01/match-com-app-store/
Most (but not all) orient around violations of Apple's developer TOS which are famously fickle and changeable. No emulators? Can't use "private APIs"? Microsoft was hauled in front of the DOJ for better. Could those using an Apple account to sign their non App Store apps be subject to similar, shifting rules about what's kosher and what's not?
And if Atari has really had apps pulled for supposedly bearing a "passing resemblance to an Atari classic", we're in weird territory. From my POV, there's just a creepy potential for blacklist first, ask questions later style arbitration on Apple's part.
As a once Apple fanboy who's still surrounded by Apple gear, this all seems a bit weird to say, but as a developer I'm not keen on this move at all.
> Can't use "private APIs"? Microsoft was hauled in front
> of the DOJ for better.
Utter bullshit.http://www.zdnet.com/news/microsoft-vs-doj-its-all-in-the-ap...
Of particular interest:
On Thursday, when the company had a chance to edit the DOJ's antitrust remedy proposal, it added language stating that "nothing in this provision shall require Microsoft to disclose any internal interfaces of a Microsoft Operating System Product."
Throughout its edits of the DOJ proposal, Microsoft tried to draw a distinction between external APIs (which the company is willing to give away and already often does) and internal APIs (which it is fighting tooth and nail to keep under wraps).
Restricting access to and the lack of documentation for private APIs was a key part of the case, although due to its technical nature, was not particularly well publicized.
In the past, Apple has done quite a nice job at still doing a lot of stuff that benefits us--probably by promoting long term user satisfaction as their recipe for success. But at the end of the day, their allegiance probably lies with the stakeholders, and many of them are more interested in short term earnings than long term investment.
If all of a sudden Apple stops making money and starts doing shady stuff then I'll look at my other options and possible switch again just like I've done before.
Sure, but this strikes me as naïve. It can take less than being nefarious to get booted off of a service (like having an Apple developer ID) like having a corporation or government agency filing a potentially unfounded complaint against you (as we've seen with YouTube videos and, this very week, Jotform's Web site.)
The problem I have with Gatekeeper isn't in the pleasant, straightforward scenario Apple wraps into its copy. The problem is giving a corporation direct control over whose apps can and cannot work on a computer by default is a set up for some depressing abuse stories that can only be rectified by turning off security or performing UI acrobatics.