Approved by URI Mobile App Advisory Committee, October 2020

Purpose

The Rhody Connect mobile app is a university-wide tool that makes the campus accessible with the tap of a button. The purpose of the app is to provide students with current and real-time information, offer simplified access to online services, and serve as a continual point of connection to campus. Driven by student input and user feedback, the app will continue to add new services and evolve in both content and functionality.

Background

In 2019, The University of Rhode Island engaged Modo Labs of Cambridge, MA to build the first university-wide mobile application, Rhody Connect. Modo Labs has previously developed apps for other universities across the country including Harvard, Brown, RISD, UMass, Notre Dame, NYU  and others.

Modo Labs develops mobile apps and offers a mobile platform that enables universities to build upon the original app as needed. Content can be added to the app in the form of new modules, which may contain information published by URI, or information distributed by another, third-party application. The platform is web-based, meaning that users will continuously get new information from the app, as long as they are connected to the Internet. This platform will allow URI to expand the app over time to include more features that meet students’ needs. 

Important Terms

  • App: The downloadable software package that users download from an app store (in this case, either the iTunes App Store or the Android Google Play store).
  • Module: Within the app, different modules allow users to access different types of information or perform different tasks (e.g., Maps, Dining, and News).

Guidelines for Mobile App Module Development

1. Branding

All modules must make proper use of the URI brand, as laid out in URI Brand Visual Standards Guide. 

2. Web Governance

All modules must follow the guidelines that cover web governance, including those policies that relate to messaging, visual content, and accessibility.

3. Audience

The app’s primary audience is University of Rhode Island students. Secondary audiences include faculty, staff, alumni, potential students, and campus visitors. Any new modules, features, and functions must enhance the existing URI app experience for those audiences.

4. User Experience

A good module will include content that engages users with timely, personalized, and actionable information for a truly interactive experience.

Users should be able to access information in a simple and touch-friendly interface. There should be a minimal number of steps for a user to reach the desired information or to perform a desired task. The design of the module should not impede the user’s ability to read important text, load screens, or navigate between different areas of the app. Touch functions like swiping and scrolling should line up with the mobile platform’s standards.

5. User-Submitted Data

Users should not need to input excessive amounts of data to access pertinent parts of the app. Any module that requests personal information or requires passwords from individuals will undergo special scrutiny from the mobile app team. When possible, authentication for external modules should be provided by URI’s Single Sign-on (SSO). At no time should users be prompted to share personal data that will then be made available to entities outside of URI.

6. Module Function Types and Purposes

In a mobile app, there are four potential types of modules:

  1. Content: A content module is generally static information or other content that does not change on a regular basis and requires manual updates.  Examples include general program information, descriptions/instructions, and statements that do not change. Static content is the least desirable module for an app – this type of information belongs on a website.
  2. Information: Live information modules change or update on a daily, hourly, or even minute by minute basis. This type of module is intended to provide real time status information for the app user so that they can plan or act based upon what is happening now.  Examples include the locations and arrival information of the campus shuttles, number & location of currently available computers in a lab, hours of operation if combined with real-time open/closed status and queue length, or upcoming feed from events that may include live news/updates or current scores from an athletic game.
  3. Service: Allows the user to interact with a campus resource or service.  These are simple opt-in, yes-no, day & time types of services.   Examples include accessing PeopleSoft or Brightspace, viewing & scheduling an appointment, reserving a study room, or reporting a facilities problem.
  4. Transaction: The highest level function for an app is to allow someone to do something that they previously would have had to do in-person or via a browser. These are functions where the app streamlines access, as the user may already be authenticated and allows for interaction with the university to accomplish a task. Examples include registering for a class, completing a payment transaction, purchasing a ticket, or registering & checking in at a ticketed/tracked event.

As a best practice, the mobile app team will be focused primarily on developing Service and Transaction level modules.  Informational modules will be considered if they provide a service to the entire student population or campus community. Outside of special events, rarely will static content modules be approved for inclusion in the app, as a statement showing a high value to the student or campus community will be required. Module submission requests should keep these functional levels in mind and the requestor should indicate which level they believe is appropriate for the proposed module. The submission form must also include sufficient information to substantiate the requested classification.

Request a Module

Sources cited:

University of Massachusetts, Boston. (2013). Mobile App Policy. Boston, MA: Mobile App Advisory Committee. https://www.umb.edu/news_events_media/communications/web_resources_feedback/mobile_app_policy

California State University San Marcos (2016). Mobile App Procedure. San Marcos, CA: Mobile App Advisory Committee. https://www.csusm.edu/iits/services/mobile-app/procedure.html