Publishing Guidelines

The UCLA Mobile App Guidelines are in DRAFT form & are Under Review: 

* DRAFT* UCLA ‘Mobile App’ Publishing Guidelines - Revised 8-17-20

Publishing apps under the official UCLA account on the iOS and Google Play stores, is governed by the following guidelines.  All apps published must comply with all University policy regarding the release of iOS/ Google Play applications.

1.  UCLA official apps are advertising free. 

UCLA will not release apps that have advertisements in them, per University Web Advertising guidelines (per IT Planning Board archive).

  • Third-party products and services are the area of concern. Using a UCLA app to promote a UCLA activity (such as Performing Arts or Athletics) is not considered advertising. 
  • UCLA Apps must not subject students, faculty, and staff to commercial messages in the conduct of UCLA’s core academic and administrative activities. More leeway is appropriate for apps related to extracurricular activities or other optional information.
  • Commercial and quasi-commercial content in UCLA’s Apps should:
    • be directly related to the core business of the university and to the specific instance of that business represented by the app in question,
    • contribute to the greater good of the university,
    • be consistent with existing policy and guidelines.

2.  UCLA Apps will conform with all UCLA policy regarding data protection, privacy and accessibility.

All UCLA built and third-party developed apps published under the official UCLA app store accounts that have or store any medical or protected health data, student protected data, Personally Identifiable Information, must go through the appropriate security, privacy and accessibility reviews.  All research apps must be IRB approved (if applicable) or gone through the appropriate level of security, privacy and accessibility reviews.

All Apps published under the UCLA account must be able to answer the following set of questions:

  1. Does the App transmit any sensitive data (including, but not limited to), and if so explain how that data in transit is encrypted:
    1. Personally Identifiable Information?
    2. Student Data
    3. Medical Data
  2. Does the app locally store any sensitive data (including, but not limited to), and if so, how is it encrypted:
    1. Personally Identifiable Information?
    2. Student Data?
    3. Medical Data?
  3. Is the app accessible, does it comply with ADA WCAG 2.0

3.  Mobile Apps published under the UCLA accounts require appropriate alignment with UCLA’s Mission and Values.

All apps published under the official UCLA app store account must align with the mission of ‘Education, Research, Service’.  All apps must also align appropriately with the true bruin values and the principles of our community.

4.  All of the apps UCLA publishes in the public apps stores require a campus sponsor, to maintain them and keep them properly functioning. 

  1. Apps require a current departmental technical support contact, who will manage their app content and upgrades on an as needed basis.
  2. Broken apps will be removed from the store and re-published once functioning properly

5.  Intellectual Property (IP) is managed in an consistent manner to all other UCLA copyrighted works.

  1. Intellectual property (IP) of apps is governed in the same way all copyrighted works are managed. 
  2. Faculty and students own their own copyrighted work.  Something to note is that any app built utilizing any university resources would have a shared IP agreement.

6.  UCLA Apps have thus far been free of charge.  Future apps that are fee-based would be governed by a UCLA Licensing agreement via UCLA's Technology Development Group.

  1. UCLA has not yet to date set up the financial accounting to collect app based revenues.
  2. Apple and Google Play collect a fixed percent (typically 30%) off the top of all app revenue.
  3. UCLA’s Technology Development Group (TDG) manages all IP and revenue-based agreements.  It is assumed they would negotiate future revenue based app agreements as well.