In order to bring some regularity and clarity to the listings found on MacUpdate.com, we’ve developed some guidelines that we adhere to as much as possible; these are the principles upon which we revise submissions. Here are some guidelines to consider when submitting apps and updates:

Permitted Markup

Bold text <strong>
Italicized text <em>
Heading text <h5>
Unordered lists <ul><li>
Ordered lists <ol><li>
URLs <a href=“link”>
Code <code>
Strikethrough <strike>

All paragraphs wrapped in <p> tags.

Title

App titles in listings should reflect only the app name as shown on the developer’s website or in app documentation and should not include version information or any extraneous words describing the app type, app function, or evaluations of the app.



Short description

Short descriptions should reflect the simplest, most concise explanation of the app’s purpose or primary function and should be no longer than a single sentence and should not include evaluative statements or anything not explicitly factual about the app.



Description

Descriptions should offer concise information about the app’s purpose, describe its distinguishing features, and identify its target users. The following is a template for a proper MacUpdate info page description, which should contain 1-2 short descriptive paragraphs and an unordered feature list.

<strong>Application Name</strong> allows users to [explain app’s primary purpose]. With Application Name, you can [list any additional key app functions]. It is ideally suited for [identify target users]Include any additional vital information that a user should consider; focus on features and benefits.

<p>If additional paragraphs are required in order to describe application, be sure they are wrapped in paragraph tags.</p>

<p>Supported file types include the following:</p>
<ul>
<li>.mp3</li>
<li>.m4a</li>
<li>.ogg</li>
<li>.flac</li>
</ul>

<h5>Heading (e.g.: Features)</h5>
<ul>
<li>Item in feature list</li>
<li>Item in feature list</li>
<li>Item in feature list</li>
<li>Item in feature list</li>
<li>Item in feature list</li>
</ul>



Developer URL

This should be a link to an app-specific product page only.



Screencasts

Screencasts must be submitted as YouTube links. At the moment, only embedded YouTube or Vimeo videos can be displayed on app info pages.



Version number

The version number in the listing must match an app’s internal version number as reported by Finder or MacUpdate Desktop. Users rely on this internal version number to have updates distributed through MacUpdate Desktop.

In order to accommodate users that rely on the internal version strings for update delivery in MacUpdate Desktop, if an internal version number does not agree with the claimed or submitted version number, the internal version number will be featured in the listing with a note included in the version changes field explaining the discrepancy.



Version Changes

Release notes for an application should be limited to a heading (New Features, Bug Fixes, Improvements, etc.) followed by an unordered list. A special note may be inserted just after the Version _.__: text to denote version discrepancies, temporary sales, paid upgrade paths, and other unique version-specific circumstances. The following is a template for proper MacUpdate info page version history, showing formatting for all acceptable scenarios.

Version _.__:
<p><strong>Note:</strong> Insert any important version-specific or update-related disclaimers here.</p>

<h5>Heading 1</h5>
<ul>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
</ul>

<h5>Heading 2</h5>
<ul>
<li>Category of change (e.g.: Interface redesign)</li>
<ul>
<li>Additional detail and info regarding change</li>
<li>Additional detail and info regarding change</li>
</ul>
<li>Category of change (e.g.: Stability improvements)</li>
<ul>
<li>Additional detail and info regarding change</li>
<li>Additional detail and info regarding change</li>
</ul>

<h5>Heading 3</h5>
<ul>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Briefly mention new feature, improvement, bug fix, etc.</li>
<li>Access the <a href=“http://fullreleasenotes.com/”>complete release notes</a>.
</ul>



Screenshots

Individual screenshots can be uploaded to listings through the app update submission form. If any screenshots are to be replaced, be sure to mention so in the Developer comments field.

If you would like to update more than one screenshot at a time, compile up to 5 screenshots and include links to them individually or as a combined archive in the Developer comments field with a brief explanation of the order in which they should be displayed. Alternately, you can email the screenshots as an archive or as attached images in a message to updates@macupdate.com; be sure to include information regarding which app listing to update, what order to display the screenshots, and which screenshots should be removed if necessary to accommodate new screenshots.



Download URLs

Submitted download URLs should be direct links to the app or an archive containing the app or its installer. Any URLs included in a listing remain as submitted and only go through a few internal redirects before reaching a developer’s site. In some cases, however, if a download URL is submitted in a format incompatible with MacUpdate Desktop’s update distribution process, a content editor will host the app on a MacUpdate server in an archive compatible with MacUpdate Desktop.

Additionally, if a download URL directs to a site requiring additional steps for download (e.g.: MediaFire, Google Drive, etc.), a copy will be uploaded to MacUpdate servers for direct access in listings. If a download URL is not direct because it links to a developer’s site requesting user information (email, reason for use, etc.) in exchange for the download, it will remain unmodified. A direct link to the app, if obtainable, will then be added to an internal URL field to work with MacUpdate Desktop since it requires a direct link to deliver updates.



License

Free: freeware or donation-ware
Demo: (can be downloaded) full app requires separate purchase, or in-app purchase if from Mac App Store
Shareware: (can be downloaded) can be licensed for full functionality
Commercial: cannot be downloaded unless purchased



Price

Prices on MacUpdate must reflect the full cost of purchasing an app outright, and cannot be updated to reflect a temporary sale or discounted upgrade path. Any notes regarding temporary or limited price changes can be made in the Version Changes section of an app listing.


In some cases, an app's price may refer to a (one-time or recurring) payment for a service that the app offers, or for full intended use of the app. When these exceptions are encountered, a note will be made in the listing's description.




Minimum OS and System Architecture

Minimum OS requirements and system architecture requirements apply to a listing’s primary download. Some apps may have multiple builds to accommodate various users’ operating systems or architecture; these can be accommodated in app listings, but become listed as app variants. The OS and architecture information that is displayed about an app in an app listing should always refer to the primarily available download.

If an app is being submitted as a 64-bit application, it needs to have a particular 64-bit build; although 32-bit applications will run on 64-bit operating systems, they will not take advantage of the additional memory benefits offered by 64-bit systems. Therefore, an app without a specific 64-bit build can only be classified as 32-bit.

Be mindful of which operating systems and architectures can be offered together; for example, an app that requires OS X 10.7 or later cannot be classified as both Intel and PPC. Here is a list of operating systems and possible architecture:

OS X 10.1 to 10.3:
PPC
32-bit

OS X 10.4 or later:
PPC
Intel (Starting with OS X 10.4.4)
32-bit

OS X 10.5 or later:
PPC
Intel
32-bit
64-bit

OS X 10.6 or later:
PPC
Intel
32-bit
64-bit

OS X 10.7 or later:
Intel
32-bit
64-bit

OS X 10.8 or later:
Intel
32-bit
64-bit

OS X 10.9 or later:
Intel
32-bit
64-bit

OS X 10.10:
Intel
32-bit
64-bit