top of page
Frame 256.png
INTRODUCTION

College offers plenty of opportunities for students to explore new things, but there is a high tendency to lose sight of different deadlines. To overcome this struggle and keep oneself consistent with courses and other curricular activities, a new digital educational platform known as EDVORA approached me to develop a calendar/timeline app for multiple devices.

TARGET AUDIENCE

Students, aged 18 to 26 pursuing different programs in universities, are actively participating in ‘on’ and ‘off-campus’ events, and want to have a more reliable and accessible system to monitor all their activities and class schedules.

PROBLEM

As a recent graduate myself, I can say that college students struggle a lot with not being able to organize and manage various aspects of their lives like school, social, personal, etc. They need constant reminders about their classes, assignments, and other events. Edvora needs a specific platform for students to prioritize their different tasks in a timely manner.

GOAL

Creating a timeline/calendar to communicate events and deadlines helps in maintaining a workload balance through proper time management.

DESIGN PROCESS
process.jpg
OBJECTIVES

  1. Show every class’s schedule and activities for the day in the calendar.​

  2. Has a sub-component that keeps track of all the events (activities and reminders) and allows the user to add new events for the desired time and place.

  3. Incorporate a week as well as month view so that users can view the calendar by their preferences.

  4. Enable the users to sort the calendar by the given fields. (Classes, reminders, events).

USER TESTING

I conducted 2 rounds of user testing. Since I was on a very tight deadline, I decided to show my current designs to only 2 people for testing and they were both college students.
The first interview was done after completing the digital wireframing. I got feedback on some minor details that I missed and some features that can be redesigned for better accessibility.
The second interview was conducted after completing the final design. I was able to showcase all the changes made and improve on anything new that was added.

CHANGES AFTER USER TESTING
Desktop and Phone Header

  1. Removed the title “Timeline” to make the best use of the space.

  2. Changed calendar view from the drop down to a toggle button since there were only 2 options to choose from.

  1. Placed all the elements in one row for the phone header.

  2. Added “Calendar” option to make it consistent with the desktop design.

Frame 246.jpg
Adding a New Event

  1. Instead of popping the window on top of the calendar for adding a new event, it slides in from the right side so that the calendar is not hidden.

  2. In case of creating a wrong event, the user had to close the window and rewrite everything. To resolve this issue I created a one-click toggle button to transition between activities, reminders, and classes. It also, auto-saves the information while switching between the events.

Frame 243.jpg
Frame 247.jpg
Weekly View

  1. For the weekly view, users wanted to add multiple events for the same time period.

  2. They also wanted the time of the event to be shown always. Therefore, I made the time slot visible underneath the title itself.

Side Bar Information

  1. “No Event Planned” was completly taken out since it was not serving any purpose to the user.

  2. To make the event list less overwhelming for the students, only 5 events were displayed per day.

  3. Added a scroll bar and “See All” option to indicate that there are more events planned for the day.

Frame 242.jpg
Frame 245.jpg
List View on Phone

  1. Since only half of the screen was showing the events, users had difficulty accessing all the events at the same time. Considering the size of the device, I created a separate screen only for the list view.

KEY TAKEAWAYS

  1. Working with tight deadlines and prioritizing events as per project requirements.

  2. Understanding the balance between the user’s expectations and stakeholder guidelines.

  3. Making the app more attractive by using multiple colors yet keeping it minimal and subtle.

  4. Design for best and worst-case scenarios.

  5. The usage of subcomponents for additional information eases the overwhelming experience.

bottom of page