Easy Rider — Transit App

People helping people have an easy ride.

Creating an app that benefits public transit and its riders

In the first portion of Hacker You's UX course I was given the task of forming an app idea that would help public transit in a positive way.

I wanted to address the need for interactive travelling on public transit. If you’re driving a vehicle you have access to apps such as Waze that allow users to interact with one another and report delays or incidents that other drivers would benefit from. I want to empower users with the most up to date information about transit from a reliable source.

I went to solve this design challenge using the 5-step Sprint Method for answering tough questions through prototyping and testing ideas with users.


I was the student/lead designer on this project. I created the Easy Rider app and design system.

The Challenge

To give users a platform to interact so they can help each other plan ahead and act in an informed way when riding transit to avoid any sudden delays.

The Solution

The solution for Easy Rider is to design an app, design system, and brand identity along with a high fidelity prototype to showcase the final product.


To start I need to map the problem and pick a place of focus, set the projects goals and the questions that will need to be answered. I did this by talking to users and looking into the competitive landscape.

During user interviews, I found that the 85% of riders interviewed would like to avoid crowds and are “frustrated” with the number of delays that occur and an overall feeling of being uninformed when riding transit.

I also found that some people would even change their work schedule to accommodate an easier commute, others even take a detour route to enjoy an easier ride. One thing became clear Toronto’s transit riders are looking for a reliable source of information in order to enjoy a comfortable ride.

There are many amazing apps out there offering parts of my intended idea. The Easy Rider concept will be a combination of Waze, Google Maps, and Transit App. I liked how Waze allows users to give each other information about traffic and the way the app gives user updates. I looked to Google when considering the map feature, and Transit App for transit route timing and API usage.

    After running through idea's, talking to users, and scoping the market I was able to define my app's goals:

  • How might we give reliable travel times?
  • How might we encourage users to add feedback?
  • How might we offer tips to travel smarter?
  • How might we save trips and addresses for customized travel information?


Now that I have a good idea of what my app is going to be, based on user interviews and feedback. I want to start sketching ideas, I need to take a combination of the idea statement, JTBD, HMW, and competitors notes and turn that into an interesting user interface.

I sketched my ideas down on paper using the crazy 8's method to present multiple options. This is an extremely rough draft drawn on a piece of paper that shows key features for users when interacting with the app.

    Screens that needed to be included in this phase:

  • Home screen (map)
  • Nearby routes with est. times
  • Reporting an incident
  • Travel tips
  • How users get alerts


This being an independent class project, I'm not working in a team or stakeholders, so I turned to trusted friends, teachers, and mentors for help with the decision phase. I had them vote on favourite solutions and used that information the same way I would in dot-voting.

Once the group decided, I took the winning sketches and ideas and put them together into a storyboard, all tightly connected to form a cohesive story from the users point-of-view.

The user story detailed below shows how a user would interact with the app during the morning commute, entering location & destination, finding out best travel times, reporting incidents, checking out best travel times, and rating rides.


When it came time for prototyping I wanted to first define brand colours, typography and iconography. From there I referenced my storyboard to create the version ready for user testing.

My vision for the design was to create a clean and simplified layout that offered a confident and reliable feeling to the user. Much of my inspiration came from the Material.io design system and when considering maps, I went straight to Google and Apple since they already established a trusted way of getting directions on our phone.

    Easy Rider Prototype Checklist

  • Define Style Guide
    • Colour Palette
    • Typography
    • Iconography
  • Design app screens in Sketch.app
  • Create a prototype with Invision


Now that I have my prototype ready to go, I can start user testing with a more refined product. I structured the interview questions in order to give the interviewee as much context as possible. I wanted to find out what is the intuitive way users navigate the app, uncover user pain points, and gather data to reframe any design challenges.

During the interview process, I learned that getting immediate current location route information is the most important to users. I also found out that Travel Tips is prefered over Best Travel Times, and that I needed to visually make tips and notifications stand out more.

    Basic overview of interview questions

  • How often do you take transit and when do you travel?
  • If you needed to find out how to get to your next destination the fastest way possible, how would you find that information?
  • If you knew you had new notifications, where would you retrieve them?
  • How would you go about submitting transit updates?
  • Between Best Travel Times & Travel Tips, which is more intuitive?


I was able to take the information gained during the testing round and make some style and layout changes. This is the perfect app for all my fellow introverts who find an overcrowded subway a major drag. This app allows users to leave a short message to describe any transit incidents involving line delays, traffic accidents, medical emergencies or any other factor contributing to a delay in your commute.

All incidents reported are available to other users via notifications, so they can begin their transit journey informed and aware of any potential barriers. Users are able to see wait times for nearby lines and get transit directions to their desired destination.

Users also have access to Travel tips and tips vary from suggested travel times to how to cope with crowded subways. This gives users the necessary tools to plan ahead and choose less crowded travel times in order to enjoy an easier commute.

Take a look at the Invision prototype to see how app interactions are intended to work, designed for an iPhone XS.

view Invision Prototype