1
Mobile Application Development Guidelines
Introduction
The growth of mobile applications (“apps”) and devices necessitates an evolution in the University of Northern Colorado’s (UNC) approach to communication with our audiences. To ensure a coordinated, cost effective approach and a coherent, quality image for the university, the following guidelines are available to assist all mobile app development efforts. All apps branded with a UNC affiliation must obtain approval of the Mobile Guidance Committee. Apps must be published centrally through the university app store accounts to allow users to easily find all UNC offerings and allow the university to remove or replace discontinued apps.
Mobile website development is part of the overall web strategy of Web Communications and all questions regarding technical aspects and identity compliance should be directed to the Office of Web Communications.
Mobile Definitions
A ǁĞďĂƉƉ is browser-based and device-agnostic and users must have internet access
(www.unco.edu) to view the pages. Native apps or mobile apps are downloaded from an app store. A native app is fully self-contained and often incorporates the functionality (e.g., camera, video or global positioning) of a device. A “hybrid” native app also is downloaded from an app store and stored on a mobile device but contains embedded programming that retrieves data from a remote server each time the app is used.
University Roles
The Mobile Guidance Committee is responsible for setting overall mobile strategy for the university, reviewing and approving mobile app requests and coordinating changes to app store offerings. Mobiles apps may be developed by third party vendors or developers. These apps must have a
university sponsor responsible for funding, planning, project completion, quality review, promotion and long term oversight of the app. Sponsors are also responsible for notifying the Mobile Guidance Committee of any change or discontinuation of app. Sponsors must obtain approval of the Mobile Guidance Committee before entering into agreement with vendors or third party developers.
Mobiles apps developed to serve university audiences may also be developed internally by faculty, staff or students and developers must obtain approval of the Mobile Guidance Committee before expending university resources on development of the mobile app.
Faculty, staff and students may develop apps that are not associated with the university or intended for university audiences and these apps must be published independently and cannot include university branding or implication of university ownership or endorsement.
2
Determining Need
Development of a mobile app can be time-consuming and expensive and campus units should carefully consider the resources required and reasons for developing the mobile app before utilizing resources for its development. Development of a mobile app should be part of a unit’s larger digital marketing
strategy and should meet an identified need of a university audience over an extended period of time. Mobile apps are intended to take advantage of specific functionalities of a mobile device, such as GPS or camera capabilities, and are not intended to simply repurpose web page content. Mobile users are often looking for specific information for just-in time needs, such as map locations or event times. For the university to consider a mobile app appropriate for publishing the university accounts on app stores, sponsor(s) of the app must establish that the work product meets strategic goals:
• Supports specifically identified objectives and goals of the university • Delivers value to one or more target audiences of interest to the university • Enhances the overall reputation of UNC
• Addresses a need best met via mobile app • Addresses a need not met by another mobile app • Is a responsible use of fiscal and human resources • Has a long term usefulness for audiences
• Does no harm to the university generally or its information technology systems, in particular
General Requirements
Each app has unique characteristics and each project therefore necessitates a conversation about specific needs and requirements. General requirements include:
• Sponsoring departments must have funding for all aspects of the app, including personnel needs.
• All apps must comply with copyright and trademark law and intellectual property and licensing considerations before release.
• Apps collecting data or requiring secure logon meet requirements of the university’s privacy policy as well as industry best practices for secure collection of data.
• Apps must meet university graphic identity standards
• App must comply with UNC standards, policies and procedures . • Apps must meet acceptable industry technical standards. • Apps must meet standards set by mobile app distributor
• Unless prior approval is granted, apps must be free of charge and cannot include advertising • Apps can connect with for-profit entities only with university permission
• Requests for access to university data must be reviewed and approved by Information Management and Technology and, when appropriate, Web Communications.
• The wording of the app About section must be approved by Web Communications. • Exclusivity requests by vendors and third party developers should not be granted.
3 • Vendor and third party agreements must include stipulations for continuation or removal of app
in case of discontinuation by vendor or third party of university.
• Projects developed internally must include all relevant development documentation, including source code, graphical assets and audio/video assets, available upon request
• Projects developed internally must include maintenance and support documentation that addresses changes to the app, core mobile operating system and/or hardware, available upon request
Initial Review
Any proposal submitted for an initial project review should include a functional and technical description of the application. Each project request contains unique elements and will require an adequate
timeframe for review. See Appendix I.
_________________________________________
Appendix
Mobile Application Project Review Form
Name of UNC campus unit (e.g., college, school, department, program or organization) for which the mobile app will be developed (this unit will be considered the mobile app sponsor):
Name and email addresses of UNC employee(s) who will serve as administrator(s)/sponsor(s) of the mobile application and be the primary contact:
Name E-mail
Name E-mail
List vendor/ third party developer name and contact information if applicable:
Describe vendor/third party qualifications if applicable:
Identify the primary audience/user group for the mobile app (select one): • alumni • athletics fans • community • employees • parents • prospective students • students • donors
4 Describe why the app is needed:
Describe in detail the proposed features, supported platforms and functionality of the mobile app: Describe the role of university personnel, including planning, development, vendor/third party communication and support:
Describe costs associated with project, including human resource needs:
Describe any proposed platform/delivery method (i.e., iPhone, Android, Windows or HTML5):
Describe any UNC software or system dependencies (e.g., Banner, LDAP, RSS feed) and UNC technical support needs:
Describe any user personal information collected and how information will be used: If applicable, describe any plans for texting users:
If user authentication is required, is a forgot password and/or username support provided? Describe any UNC graphic design support needed:
Describe any proposed advertising or merchant involvement if appropriate: Describe how the effectiveness of the app will be evaluated:
Describe how you plan to promote the mobile app:
Describe how you plan to maintain and upgrade the mobile app: Describe proposed timeline for availability of app:
__ I have researched the vendor on the Better Business Bureau or other consumer advocate sites (please list sites).
___________________________________________________________________________
Development Process
Throughout the development phase, the UNC developer or sponsor is expected to meet with the Mobile Guidance Committee at identified milestone points. The purpose of the meetings is to ensure that the mobile app aligns with the proposal and allows the involved parties to address any issues that may arise as work progresses.
5
Technical Review
Once development has been completed and before publication, the app must be presented to the Mobile Guidance Committee for technical review in a testing environment. The review will include but is not limited to:
• security
• feasibility of any required UNC data availability • method and techniques of execution
• mobile device impact
• university technology system impact • local and remote data integrity
• generational device and mobile operating system support
• adherence to mobile application distributor guidelines and best practices • adherence to university identity standards
• quality assurance testing
• quality and availability of documentation • support strategy
Distribution
Once approved, mobile apps must be distributed centrally through the UNC license for app stores. Web Communications will assist with the distribution of the app to ensure proper placement. Please be advised that each app store has a timeframe for review before the app is approved. Approved apps will be listed on the university’s mobile promotion page.
Compliance of Apps
If an app is found to be out of compliance with university guidelines, the university can request that a sponsor facilitate changes or remove an app, remove the app from the approved list, revoke permission to use UNC branding or take other appropriate steps to resolve the problem.
