Mobile Applications

U-M Tech Transfer is the gateway for publishing mobile apps for the University of Michigan and is responsible for publishing apps developed by or sponsored by U-M faculty, staff and graduate students. Tech Transfer can provide value and assistance throughout the publishing process, including the following:

  • Determine if your application is university-owned
  • Provide best practices and other points to consider when developing your app
  • Review privacy policy elements and assist if needed
  • Determine potential need for IRB, FDA, or HIPAA regulatory compliance
  • Assist with licensing considerations and process
  • Provide guidance on requirements to submit your app to the Apple App Store and/or Google Play Store.
  • Share analytics as desired while your app is live.
  • Update apps as needed.
  • Determine a maintenance plan for your app.

For more information on mobile publishing, please call 734.764.0614.

Is Tech Transfer responsible for publishing your app?

If the developers or sponsors of your app include U-M faculty, staff, or graduate students, then Tech Transfer is likely responsible for publishing the app. If Tech Transfer is publishing your app, please complete and submit an invention disclosure form online or manually here. We cannot start the publishing process without a complete invention disclosure form.

Before Publishing

  • Involve Tech Transfer early in the process. When you have an idea, talk to Tech Transfer to walk through requirements and potential considerations.
  • Develop a privacy policy. Tech Transfer can provide a template if desired.
  • Determine if IRB, FDA, or HIPAA compliance applies. Mobile applications deemed likely to meet the definition of an FDA-regulated medical device can only be published under IRB or similar oversight.
  • Complete a U-M branding review if you play to use U-M branding in your app. Tech Transfer can provide you with contact information.
  • Consider accessibility as you develop your app. Some resources can be found at
  • End User Licensing Agreements (EULAs). Tech Transfer can assist in evaluating licensing considerations.
    • While U-M typically uses the standard Apple and Google EULA, you may want to consider using a custom agreement
    • Custom EULAs are typically required for medical apps, apps that involve HIPAA regulation or apps entailing FDA regulation

Royalty and Revenue Distributions

Both Apple and Google receive a 30% commission on the net sales for all applications. Royalty and revenue distributions are handled according to the standard Tech Transfer process on the remaining 70%.

Publishing Process Overview (iOS and Android)

U-M Information and Technology Services (ITS) and TechTransfer work together submit your source code and other required assets for publication to the App Store and Google Play Store.

Generally, three types of submissions can be made:

  • New app.  The primary elements required for publishing a new app are the app’s
    • Source code
    • Graphics assets (screenshots, icons, etc.)
    • Metadata
    • Privacy policy
  • App update. The primary elements required for updating an existing app are the app’s
    • Updated source code
    • Release notes (what’s new)
    • Graphics assets (screenshots, icons, etc.), if applicable
    • Updated metadata and privacy policy, if applicable
  • Beta testing. Both iOS and Android apps can be submitted for beta testing prior to release to the stores. The primary elements required for testing is similar to that for new apps and app updates
    • Source code
    • Information for testers on what to test
    • Graphics assets (screenshots, icons, etc.) – required for Android only
    • Metadata
    • Privacy policy
    • List of testers’ email addresses

Tech Transfer will provide you with a detailed app submission form so that you can provide us with the source code and assets necessary to submit your app to the stores for review and approval. After the app is submitted for review and approval, Tech Transfer will apprise you of the status throughout the process.

Apple and Google do not provide specific time frames for their app review, and review times may vary by app. Apple reports that on average, 50% of apps are reviewed within 24 hours and over 90% are reviewed in 48 hours.

iOS App Submission – Detailed Requirements

This section lists the information required to submit a new app, update an app, and to submit an app to TestFlight for beta testing.

New iOS App

  • Source code
  • Version number
  • Primary Language
  • Bundle identifier. Format MUST be: edu.umich.xxx, where xxx is the name you have used
  • Name of app (NOTE: The name that shows up under the icon in the App Store is the PROJECT NAME in the source code. Try to keep it both short (12 characters or fewer, approximately) and descriptive. Maximum of 30 characters with spaces.)
  • App subtitle (optional) (A summary of your app that appears below your app name throughout the App Store in iOS 11 or later and the Mac App Store in macOS Mojave or later. A subtitle can be up to 30 characters long and appears below your app’s name throughout the App Store.)
  • Price (if any) of the app
  • Description of the app, detailing features and functionality (4000-character limit)
  • Keywords (100 characters max, including spaces and commas between the words)
  • Support URL
  • Marketing URL (optional)
  • Privacy Policy URL
  • 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, choose from one of the primary categories above)
  • Provide the appropriate person’s name, email address AND phone number for App Store review support (This information DOES NOT appear in the store listing)
  • Notes to be provided for the App Store review OPTIONAL)
  • If credentials are required to access the app or anywhere within the app a Demo Username and Password are required
  • Rating information – FOR THE ITEMS BELOW, please answer “none”, “Infrequent / Mild”, or “Frequent / Intense”
    • Cartoon or fantasy violence
    • Realistic violence
    • Prolonged graphic or sadistic realistic violence
    • Profanity or crude humor
    • Mature / suggestive themes
    • Horror / fear themes
    • Medical / treatment information
    • Alcohol, tobacco, or drug use references
    • Simulated gambling
    • Sexual content or nudity
    • Graphic sexual content or nudity
  • Does your app provide Unrestricted Web Access? (YES or NO)
  • Does your app contain Gambling and Contests? (YES or NO)
  • REQUIRED SCREENSHOTS
    • REQUIRED: 6.5-inch device size (iPhone Xs Max, iPhone XR): 1242 x 2688 pixels (portrait) or 2688 x 1242 pixels (landscape) at least 72 DPI, in the RGB color space, and in the JPG or PNG format. (Required; iOS can resize for 5.8-inch devices)
    • REQUIRED: 5.5-inch device size (iPhone 6s Plus, iPhone 7 Plus, iPhone 8 Plus): 1242×2208 (portrait) or 2208×1242 pixels (landscape), at least 72 DPI, in the RGB color space, and in the JPG or PNG format. (Required; iOS can resize for 4.7-inch devices, 4-inch devices, 3.5-inch devices)
    • REQUIRED IF BUILT FOR iPad: iPad images (12.9-inch iPad Pro 3rd generation and 12.9-inch iPad Pro 2nd generation) SPECIFICATIONS BELOW
      • 9-inch (iPad Pro (3rd generation)): 2048 x 2732 pixels (portrait), 2732 x 2048 pixels (landscape), iPad Screenshots must be .jpg or .png file, and 72 dpi, RGB color space, no transparency.
      • 9-inch (iPad Pro (2nd generation)): 2048 x 2732 pixels (portrait), 2732 x 2048 pixels (landscape), iPad Screenshots must be .jpg or .png file, and 72 dpi, RGB color space, no transparency.
    • Apple Watch (required for Apple Watch apps) – one of the following: 312 x 390 pixels (Series 3) or 368 x 448 pixels (Series 4)
  • Should this application automatically be released upon approval? If no, please provide information regarding the desired release timing (manual release or release on a specific date and coordination with Google Play Store Android release if applicable).
  • Does the app use IDFA (Advertising Identifier)?
  • Describe ANY encryption technology used in the app, including: communications over HTTPS; use of iOS’s built in encryption technologies (like Keychain); or any embedded encryption. This response is VERY important; export of encryption technology is highly regulated and export control regulations apply to apps distributed outside of the US.
  • If ANY encryption technology is used in the app, please answer the following
    • App uses ATS or makes a call to HTTPS (Yes or No)
    • App uses encryption limited to that within the Apple operating system (Yes or No)
    • Encryption is specially designed for medical end-use (Yes or No)
    • Encryption is limited to intellectual property and copyright protection (Yes or No)
    • Encryption is limited to authentication, digital signature, or the decryption of data or files (Yes or No)
    • Encryption is specially designed and limited for banking use or money transactions; or limited to fixed data compression or coding techniques (Yes or No)
    • App uses an industry standard algorithm not provided within the Apple operating system (Yes or No)
    • App uses proprietary encryption algorithms not accepted by international standard bodies (such as IEEE, IETF, or ITU) (yes or No)
  • What information does the app collect that you have access to?
  • Does your app contain, display, or access third-party content? If yes, do you have all necessary rights to that content or are you otherwise permitted to use it under the laws of each App Store territory in which your app is available?

iOS App Update

  • Updated source code
  • Version number that you would like to appear in the App Store listing
  • Release note (what’s new) for the update
  • Updated screenshots (optional)
  • Any updates to previous metadata (for example, privacy policy, app description, keywords, app name, demo sign-in credentials, etc.)
  • Have you added or made changes to encryption features since you last uploaded a binary for this product?
  • Does the app use IDFA (Advertising Identifier)?

iOS App TestFlight Beta Testing

  • Source code
  • Bundle identifier. Format MUST be: edu.umich.xxx, where xxx is the name you have used
  • Name of app: (NOTE: The name that shows up under the icon in the Apple iTunes store is the PROJECT NAME in the source code. Try to keep it both short (12 chars or under, approximately) and descriptive. Max of 30 characters with spaces.)
  • Beta app description. (Provide a description of your app that highlights its features and functionality.)
  • Feedback email address. (TestFlight beta testers can send feedback to this email address. It will also appear as the reply-to address for TestFlight invitation emails.)
  • Marketing URL. (A URL with information about the app you are adding. This URL will be visible to testers in the TestFlight app.)
  • Privacy Policy URL (A template policy is available if needed)
  • Beta App Review Information: Contact information — please provide a contact name, phone number and email address if the App Review team has any questions or needs additional information.
  • Beta App Review Information: Sign-in information — please provide a user name and password for the App Review team, if applicable.
  • Beta App Review notes: OPTIONAL — Additional information about the app that can help during the review process. Do not include demo account details. Review notes cannot exceed 4000 characters.
  • Test information (Include information about what’s been added to this build, and what you would like your users to test.) — this field cannot be left blank, but the beta app description can be used if you do not have anything specific to include.
  • Email addresses for the testers you would like to be invited to test the app.
  • Notify testers automatically after beta app review approval?
  • Does the app use IDFA (Advertising Identifier)?
  • Is your app designed to use cryptography or does it contain or incorporate cryptography?
  • Describe ANY encryption technology used in the app, including: communications over HTTPS; use of iOS’s built in encryption technologies (like Keychain); or any embedded encryption. This is VERY important, as export of encryption technology is highly regulated and export control applied to apps distributed outside of the US.
  • If ANY encryption technology is used in the app, please answer the following
    • App uses ATS or makes a call to HTTPS (Yes or No)
    • App uses encryption limited to that within the Apple operating system (Yes or No)
    • Encryption is specially designed for medical end-use (Yes or No)
    • Encryption is limited to intellectual property and copyright protection (Yes or No)
    • Encryption is limited to authentication, digital signature, or the decryption of data or files (Yes or No)
    • Encryption is specially designed and limited for banking use or money transactions; or limited to fixed data compression or coding techniques (Yes or No)
    • App uses an industry standard algorithm not provided within the Apple operating system (Yes or No)
    • App uses proprietary encryption algorithms not accepted by international standard bodies (such as IEEE, IETF, or ITU) (Yes or No)

Android App Submission – Detailed Requirements

This section lists the information required to submit a new app, update an app, and to submit an app to in a test track for testing.

PLEASE NOTE: Distribution of applications in China via Google Play Store is not supported. Due to government restrictions on content and the market deployment approaches in China applications that require this market are not supported. Our office continues to evaluate options for this but currently no acceptable substitutes which provides consistent market coverage and approaches are available.

  • Source code (.apk file)
  • Title: (up to 50 characters)
  • Short Description: (up to 80 characters)
  • Long Description: (up to 4000 characters)
  • App Price
  • Does your application have ads? Confirm YES or NO (If Yes, users will be able to see the “ads” label on your application in the Play Store)
  • Target audience and content: What are the target age groups of your app? (18+, 16-17, 13-15, 9-12, 6-8, 0-5)
  • Appeal to children: Could your store listing unintentionally appeal to children (yes or no)?
  • App access: are parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication? If “YES,” provide instructions on how to access them. (For example, provide demo sign-in credentials, if applicable.)
  • REQURIED GRAPHICS
    • SCREENSHOTS (REQUIRED) — at least 2 screenshots are REQUIRED overall. Max 8 screenshots per type
      • JPEG or 24-bit PNG (no alpha). Min length for any side: 320px. Max length for any side: 3840px. Max aspect ratio 2:1.
      • Screenshots can be specific to: Phone, 7-inch tablet (Only upload tablet screenshots if your app is designed for tablets), 10-inch tablet (Only upload tablet screenshots if your app is designed for tablets), TV
    • HI-RES ICON (REQUIRED) — Hi-res icon. Final size: 512px x 512px, Format: 32-bit PNG, Color space: sRGB, Max file size: 1024KB, Shape: Full square – Google Play dynamically handles masking. Radius will be equivalent to 20% of icon size, Shadow: None – Google Play dynamically handles shadows.
    • FEATURE GRAPHIC (REQUIRED) — Feature Graphic – 1024 w x 500 h, JPG or 24-bit PNG (no alpha)
  • OPTIONAL GRAPHICS
    • (OPTIONAL) Promo Graphic – 180 w x 120 h, JPG or 24-bit PNG (no alpha)
    • (OPTIONAL) TV Banner – 320 w x 180 h, JPG or 24-bit PNG (no alpha)
    • (OPTIONAL) Promo Video (YouTube video, Please enter a URL): optional
  • CATEGORIZATION (select one) – Application or Game?
  • Category, choose one: Art & Design, Auto & Vehicles, Beauty, Books & Reference, Business, Comics, Communication, Dating, Education, Entertainment, Events, Finance, Food & Drink, Health & Fitness, House & Home, Libraries & Demo, Lifestyle, Maps & Navigation, Medical, Music & Audio, News & Magazines, Parenting, Personalization, Photography, Productivity, Shopping, Social, Sports, Tools, Travel & Local, Video Player & Editors, Weather
  • CONTACT INFORMATION
    • Website (optional)
    • App Support email that will be publicly displayed in the store listing
    • Phone Number that will be publicly displayed in the store listing (optional)
  • Privacy Policy URL
  • Select an App Category: Reference, News or Educational; Social Networking, Forums and UGC Sharing; Consumer Store or Commercial Streaming Service; Game; Entertainment; Utility, Productivity, Communication or Other
  • CONTENT RATING QUESTIONS (Questions do not refer to user-generated content.)
    • Violence: Can/does the app contain violent material?
    • Sexuality: Can/does the app contain sexual material or nudity (except in a natural or scientific setting)?
    • Language: Can/does the app contain any potentially offensive language?
    • Controlled Substance: Can/does the app contain references to or depictions of illegal drugs?
    • Promotion of age-restricted products or activities: Can/does the app focus on promoting items or activities that are typically age-restricted such as cigarettes, alcohol, firearms or gambling?
    • Does the app natively allow users to interact or exchange content with other users through voice communication, text, or sharing images or audio?
    • Does the app share the user’s current physical location with other users?
    • Does the app allow users to purchase digital goods?
    • Does the app contain any swastikas, other Nazi symbols or propaganda deemed unconstitutional in Germany?
    • Is the app a web browser or search engine?
  • Is your app designed to use cryptography or does it contain or incorporate cryptography?
  • Describe ANY encryption technology used in the app, including: communications over HTTPS; use of iOS’s built in encryption technologies (like Keychain); or any embedded encryption. This is VERY important, as export of encryption technology is highly regulated and export control applied to apps distributed outside of the US.
  • If ANY encryption technology is used in the app, please answer the following
    • App uses ATS or makes a call to HTTPS (Yes or No)
    • App uses encryption limited to that within the Apple operating system (Yes or No)
    • Encryption is specially designed for medical end-use (Yes or No)
    • Encryption is limited to intellectual property and copyright protection (Yes or No)
    • Encryption is limited to authentication, digital signature, or the decryption of data or files (Yes or No)
    • Encryption is specially designed and limited for banking use or money transactions; or limited to fixed data compression or coding techniques (Yes or No)
    • App uses an industry standard algorithm not provided within the Apple operating system (Yes or No)
    • App uses proprietary encryption algorithms not accepted by international standard bodies (such as IEEE, IETF, or ITU) (Yes or No)

Android App Update

  • Updated source code
  • Release note (what’s new) for the update
  • Updated screenshots (optional)
  • Any updates to previous metadata (for example, privacy policy, app description, app name, demo sign-in credentials, etc.)
  • Have you added or made changes to encryption features since you last uploaded a binary for this product?

Android App Testing

  • Source code
  • All graphics and metadata that are required for a new Android app submission are required for a testing submission as well.
  • Email addresses for the testers you would like to be invited to test the app.