Yesterday, at Apple’s “Back to the Mac” press event, the company announced an App Store for the Mac, similar to the stores it already runs for the iPhone, iPod Touch and iPad within iTunes. There’s no doubt a computer-based “app store” is an interesting concept, and it will likely attract developers because of the exposure it provides, not to mention the hassles it eliminates – like dealing with credit card processing, or paying for hosting and bandwidth bills.
As with the iTunes App Store, developers receive the standard 70/30 (developer/Apple) revenue split on app sales. Also like the iTunes App Store, Apple has created a long list of apps it plans to reject.
Thanks to an anonymous person, the entire contents of Apple’s Developer Agreement have been posted to the website pastie.org, a site which functions as sort of a Web-based clipboard for sharing notes.
The list of apps Apple won’t allow in its Mac App Store is long. Some of the reasons are relatively standard – for example, apps that cause damage to the device, utilize Apple trademarks, apps that don’t work, etc. won’t be allowed.
However, some of the Mac Store guidelines are less about consumer protection, and more about Apple’s own version what it wants, as a company, to promote. Some call this “censorship,” some call it “curation.” Regardless of your position on the matter, it’s clear the Mac App Store will abide by similar rules as the iTunes store. In fact, in reviewing the document, it looks like Apple cut-and-pasted quite a bit of the iTunes App Store Guidelines into the the new document.
Here are some standout, and perhaps questionable, examples of what Apple will reject from its Mac App Store:
- Apps with “Easter Eggs:” Apps that include undocumented or hidden features inconsistent with the description of the app will be rejected.
- No beta apps: Apps in “beta,” “trial” or "test” versions will be rejected.
- No duplicate apps: Apps that duplicate apps already in the App Store may be rejected, particularly if there are many of them.
- No drinking/drugs: Apps that encourage excessive consumption of alcohol or illegal substances will be rejected.
- No License Keys: Apps that require the entry of a license key will be rejected.
- No Java?: Apps that use deprecated or optionally installed technologies (e.g. Java, Rosetta) will be rejected.
- No auto-run: Apps that are set to auto-launch or have other code automatically run at startup or login without user consent will be rejected. Similarly, apps can’t automatically add their icons to the dock or desktop.
- No copying Apple!: Apps that look similar to Apple Products or apps bundled on the Mac, including the Finder, iChat, iTunes and Dashboard, will be rejected.
- OS X may not be changed: Apps that change the native user interface elements or behaviors of Mac OS X will be rejected.
- No rentals: Apps containing “rental” content and services that expire after a limited time will be rejected.
- No RSS Readers?: Apps that are simply Web clippings, content aggregators, or a collection of links may be rejected.
- No data collection: Apps cannot transmit data about a user without obtaining the user’s prior permission and providing the user with access to information about how and where the data will be used.
- No Chatroulette clones?: Apps that include games of Russian roulette will be rejected.
- Define “objectionable:” Apps that present excessively objectionable or crude content will be rejected.
- No porn: Of any kind. (Porn as it’s defined by “Webster’s Dictionary,” that is).
- No gambling: Of any kind.
- No file-sharing: No P2P apps – apps that enable illegal file sharing will be rejected.
- Religious apps must be for educational purposes only: Apps may contain or quote religious text provided the quotes or translations are accurate and not misleading. Commentary should be educational or informative rather than inflammatory.
You can read the entire list of guidelines here on pastie.org or by clicking through to the next page.
Pages: 1 2
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.