R.I.S.E. Academy Web App

OVERVIEW

Our team of 5 was tasked with the design phase of a web application for an online alternative school. We were given user testing and other research that a previous team had conducted, and we had 11 weeks to create an app prototype.

Here I will highlight some of the parts of the app that I’m most proud of, but of course I won’t be able to cover everything. I’d love to tell you more about this design, so if you’re interested in hearing the details then please drop me a line

MY CONTRIBUTION

In the research and analysis phases of our design period, the entire group worked closely together to ensure that we were all on the same page. Ultimately, we decided we could better meet our tight deadlines by separating the work, and the Administrator screens were delegated to me. 

That said, every person in the team still had a say in the design, so while I may have designed a good portion of the content that is visible in the prototype, there were many contributions from my teammates (and vice-versa, regarding elements that I consulted on). Notably, the colour scheme and general UI was designed by my teammates, but I laid out each of the screens referenced here and was responsible for the planning that went into them.


Home & Calendar

FEATURES

Enables Administrators to set and edit events and choose which account types can view those events. 

BACKGROUND

While this is the first page an Administrator would see when logging in, it was one of the last pages designed. 

Through wireframing the app, I realized that we had created features to track Facilitator submissions (e.g., a feature that showed whose report card marks were overdue), but there was no easy and global way to set those due dates. 

I needed a way to not only set calendar events that would appear in the “My Calendar” portion of every user’s UI, but to define semester dates and, by extension, report card due dates. 


Templates Database

FEATURES

Allows Administrators and Facilitators to easily assign projects to students, as well as view and modify them as needed.  

BACKGROUND

Easily the heaviest part of the design, the Templates Database was my solution to a very inefficient system of creating custom assignments for students that involved rooting around folder systems on Google Drive. 

I first designed the flow for the Templates Database for the Facilitators as they would be using the system the most and it had to fit their needs (which were mostly to not have to dig through folders to find an assignment template, copy it, dig back out of the folders, dig into the student folder, and paste that assignment in there).

Once this flow was completed and approved by the client, I ported it to the Administrator flow and began adding other requirements such as Rubric and Curriculum Expectations management.

The final prototype allows Administrators to view all existing Project Templates, Rubrics, and Curriculum Expectations; modify any of those templates freely; and create new templates easily while conforming to Ontario Ministry of Education standards.