Common Pitfalls for App Developers

The following is a brief compilation of policy violations for which applications are often denied. This list is by no means exhaustive, and it is highly recommended that you go through the MySpace Application Guidelines at least once before beginning development.

• Do not publish features which are not yet implemented. This cannot be emphasized enough. Your application will be denied for incomplete functionality. On the other hand, features can be added later, once they are complete. Publishing new features will not impact your live app - users will continue to use the previous version. Once the changes are approved, the new functionality will become visible to them.

• Applications cannot contain or require any downloads or installations. The only exceptions to this rule are Macromedia Flash and Microsoft Silverlight.

• If an application contains restricted content, the appropriate age restriction must be applied by editing the app details. This age limit must also be mentioned on the Application Profile page (you can do this by logging into MySpace as the application). Such restrictions include:
  • 18+ age limit for dating apps
  • 18+ age limit for apps which contain any type of chatting functionality
  • 21+ for content related to alcohol or tobacco

• Applications cannot use a flashing icon for their logo (must be a static image).

• Applications cannot award prizes or provide the ability to cash out, return or convert money into anything of value (e.g., gift certificates, discount coupons, etc.).

• If your application contains user-generated content (such as image or file uploads, forum or message boards, etc.), or if it involves any type of monetary transaction, it must have a clear, and easily discoverable area for users to report abuse.

• Once published, live apps may not be changed substantially from their original purpose and functionality. Code changes may be be made only to fix bugs and provide enhancements to existing application functionality. Excessive, irregular, and/or large changes to code may result in suspension or deletion of that application.

• Applications cannot contain any form of search box that searches outside of the application's proprietary information or display search results with sponsored results.

Surfaces

• ALL surfaces must be unique - in both content and functionality. This means that simply changing or adding an image on one surface is not enough. Be innovative. There's a great blog on application views which could offer some insights, and help you understand the differences between each of the surfaces.

• Applications cannot contain advertisements on their Home or Profile surfaces, or on the App Profile page.

• Make sure to test for the scenario when a visitor (who does not have the application installed) visits the profile of a user. Make sure that the profile surface loads in this scenario, and that all links (including the application title) function correctly. In order to perform this test, you will have to add another developer account to the application (using the Manage Developers link).

External References & Links

• The home and profile surfaces cannot contain IFrames, or references to external JavaScripts, other than other than a library hosted by MySpace, a Google-hosted AJAX library or YUI Library Component Files.

• You can only IFrame a site which you have rights for.

• Links to external sites must always open in a new window.

Browser Functions

• The functionality of any browser button must not be hindered. That means the Back button, etc. must work correctly. Make sure to test this when a visitor interacts with the profile surface as well. This is a mistake seen very often.

• No Windows alerts or pop-ups are allowed.
  • This includes pop-ups that appear in ads, or which appear when the user tries to close an external window. Please remember that developers are responsible for all content which appears in their applications – including third party ads.
  • The only exceptions to the pop-up rule are the following browser alerts:
    • File upload / Browse
    • Print
    • RSS / Bookmarks: These are only allowed if they are contained within the browser, and if the application degrades gracefully for browsers which do not support these features.

Messaging

• In an effort to provide the best possible experience to users, MySpace has a strict no-spamming policy, and this extends to applications. This means, in a nutshell, that applications cannot incentivize users to send messages, invitations, bulletins, comments, surveys, or any other form of communication or profile post/update to earn prizes, points, virtual money, a ranking, or any benefit within or outside the application. Messages cannot pre-select options for user communications, or be vague or unclear about messaging. Users must be made aware, prior to initiating any action, of both the form and content of that action, whether they are posting to their own profile, sending a comment or message, or posting a bulletin. (e.g., "Share with your friends" is not allowed, but "Post a bulletin to your friends" is acceptable.) The options to send or cancel a message must of equal prominence.

• All messaging must be either within the app, or must use the MySpace OpenSocial APIs and/or the MySpace RESTful APIs. Applications must never ask the user to enter friends' email addresses.

• Apps cannot ask a user to send a message or communicate with another user as the first action in the app, or before the User actually uses the application for its express purpose. This also means that the express purpose of any application cannot be messaging.

Again, these are just some of the more common mistakes pointed out in applications. All applications must comply with the MySpace Application Guidelines and the Developer Terms of Service.