Status of this Document
This is a draft of the Emory Mobile Application Review Process. This document describes the process in use, but this process has not yet been documented. Once this document is finalized, it is anticipated that the Emory units involved in this process will meet to adjust and recommend a formal review process and present that to appropriate governance groups.
Step 1: Office of Technology Transfer Intellectual Property Analysis
Emory units desiring to release mobile applications should contact the Emory Office of Technology Transfer (OTT) for a review of the intellectual property and commercial prospects of the application. This process includes completion of an IP disclosure. In general, any application owned by Emory will be released under the Emory brand and through the Emory App Store or Marketplace accounts. There may be exceptions to this general rule in the case of collaborations between Emory and other partners or in a case where technology has been licensed to a third party. Typically, OTT will kick off this review process and coordinate the review with the other units listed in steps 2, 3, and 4 below. Panya Taysavang (email@example.com) is the primary contact with OTT.
Step 2: Communications & Marketing Branding Review
Mobile applications that are to be released under the Emory brand undergo a branding review with Communications & Marketing. Communications & Marketing will be preparing a set of written guidelines and resources for the proper branding of Emory mobile applications. Stanis Kodman (firstname.lastname@example.org) is the point of contact with Communications & Marketing.
Step 3: Legal Counsel Review
Step 4: Office of Information Technology App Store Posting Review
The Emory Office of Information Technology performs a high-level technical review of the application to determine if there is a need for any detailed security and compliance reviews of the application. For example, if the application collects and stores ePHI, credit card information, or other compliance related data, Emory OIT will inform the owners of the application of relevant policies and any practices required by those policies. See the template for this cursory review. Daniel Palmer (email@example.com) is the contact person for the OIT posting review.
Once this technical review is completed, Emory OIT publishes the application on behalf of Emory University. OIT needs the following artifacts from the application owners in order to submit applications:
Apple App Store
When you are ready to submit to the App Store there are artifacts that must accompany the submission to Apple.
- App Name - This is the name as it will appear in the App Store
- Availability Date - The date that the app will appear in the App Store if approved by Apple
- Price - How much are you going to charge for your app
- Educational Discount - Do you want offer a discount to educational institutions when they purchase more than a single version?
- Worldwide Availability - By default apps are available in all countries. Specify what countries this should be available in if you are choosing to restrict your app
- Version Number - A public version number, can be different than internal, strictly for use in the App Store accounting.
- Copyright - The name of the person or entity that owns the exclusive rights to the app, preceded by the year the rights were obtained (for example, "2008 Acme Inc.")
- Primary Category - (Book, Business, Catalogs, Education, Entertainment, Finance, Food & Drink, Games, Health & Fitness, Lifestyle, Medical, Music, Navigation, News, Photo & Video, Productivity, Reference, Social Networking, Sports, Travel, Utilities, Weather)
- Secondary Category (Optional) - (Book, Business, Catalogs, Education, Entertainment, Finance, Food & Drink, Games, Health & Fitness, Lifestyle, Medical, Music, Navigation, News, Photo & Video, Productivity, Reference, Social Networking, Sports, Travel, Utilities, Weather)
- For each of the following provide the frequency of occurrence in your app. Options are (0)None, (1)Infrequent/Mild, (2)Frequent/Intense
- Cartoon or Fantasy Violence
- Realistic Violence
- Sexual Content or Nudity
- Profanity or Crude Humor
- Alcohol, Tobacco, or Drug Use or References
- Mature / Suggestive Themes
- Simulated Gambling
- Horror / Fear Themes
- Prolonged Graphic or Sadistic Realistic Violence
- Graphic Sexual Content and Nudity
- Description - A description of the app you are adding, detailing features and functionality. Descriptions cannot be longer than 4000 characters
- Keywords - One or more keywords that describe the app you are adding. When users search the App Store, the terms they enter are matched with keywords to return more accurate results. Separate multiple keywords with commas. Keywords cannot be edited once your binary is in review and cannot be longer than 100 bytes.
- Support URL
- Marketing URL (optional)
- Contact Information
- First Name
- Last Name
- Email Address
- Phone Number
- Review Notes (Optional) - Additional information about your app that can help during the review process. Include information that may be needed to test your app, such as app-specific settings and test registration or account details. The Review Notes field must not exceed 4000 bytes
- Demo Account Information (Optional) - The username and password for a full-access account. This account is used during the app review process and must not expire. Details for additional accounts should be included in the Review Notes field
- EULA -
- Will you use the default (http://www.apple.com/legal/itunes/appstore/dev/stdeula/)
- If you are going to use a custom it must meet a minimum of http://www.apple.com/legal/itunes/appstore/dev/minterms/ and be properly localized to meet local legal and language requirements.
- Specify countries in which your custom EULA will be used. All countries not specified will use the default EULA
- Large App Icon -
- Must be the following
- 1024 x 1024 pixels
- minimun of 72 DPI
- in RGB color space
- must be .jpeg, .jpg, .tif, .tiff, or .png
- flat artwork without rounded corners
- 3.5 Inch Retina Display Screenshots
- Must be the following
- 960 x 640
- Must be the following
[Daniel add list here]