Public Transport App

In cities and towns across the world, public transportation plays an important role in the lives of residents and visitors alike

Year

2021

Agency

None

Project Type

UX, UI, Product Design

Role

UX/UI Designer

Overview

A Public Transport Application

In cities and towns across the world, public transportation plays an important role in the lives of residents and visitors alike. Buses, subways, trains, and other public vehicles are designed to make life easier for everyone. From improved community health to affordability, public transportation systems create the foundation on which cities become more livable and prosperous in a variety of ways.

Problem

The public transport system in my city is outdated and slow. People are losing a lot of time just to fill their cards with more trips. Bus timetable are not accurate and this creates extra stress in people's daily life. Also the digital transport card is ....

Possible Solution

Integrates features to solve user pain points. Simplifying the process of finding ideal bus, showing estimate arrive time, giving option to fill up the card without the duty to go and wait in lines. Saving time and doing the public transportation more accessible and enjoyable to the people.

View Final Solution
My Role/Responsibilities

UX research, UI design, User testing

Process

Discover

Day 1 - Define the challenge and produce solution

Users interview and HMW questions:

I have selected people between 15-50yo as the users, who use public transport daily. I chose this category of people to understand the pain points and their day to day challenges. I interviewed five people about their daily experience using the public transport.

HMW Questions
01

How can we show the bus map and the most convenient one ?

02

Create easy solution for public transport cards ?

03

Make it easier to add money to your public transport card ?

04

Motivate more people to use public transport?

Long Term Goal:

The long term goal I specified is easy to use app bringing a one-stop solution for every problem users face in order to use public transport. From this we can also speak in figures.

- 30% more people to use the public transport
- Reducing the city traffic by reducing the cars.

Sprint Questions

Sprint questions are like HMW questions, but they are more specific and designed to help identify the obstacles that might prevent us from reaching our long-term goal.

sprint questions
01

Can we remove the emotional blockers and psychological barriers in the users ?

02

Can we make the application simple and easy to use by all people ?

03

Can we gain trust and delight in using the public transport ?

Map

I drew the map to help visualize the flow of the user and have a full picture of how they will interact with the product. I split it into several important steps: Discover about the application, deciding to learn more about it, the main use of the app for them, and their main goal - to travel by bus.
In pictures bellow map for two of my participants.

Lightning demos

After a small coffee break I did the Lightning demos. The goal of this exercise is to generate a pool of ideas that the team will later use to produce their solutions. Since we all know that almost any new idea is just a new combination of a few existing ideas. I did good research and introduced the examples of how other products work: Google maps, TrainLine, Uber, these were just a few examples.

4 part sketching

The first day ends with generating the solutions. It’s done in 4 steps. The first three of them — Note taking, Doodling and Crazy 8s — are warm-up exercises, they are designed to flex the visual communication muscles of the team. I ended up with decent concept, it consist of three main steps.

Define

Day 2 — Possible Solutions and Storyboard

The bad thing about working alone is that I get to decide which concept stays and how the information is structured. After my vote I decided which concept to continue to wireframe phase.

Solution presentation

The key idea of this simple concept was to start with the main screen which is our route map, where we can add our current location and our desired location, after that we can choose which bus to choose based on the time and location. The user should navigate from the tab menu. And the steps to add more money to your card are very simple. Plus the system allowed cheching your public transpord card and adjusting how much tickets you want to buy, also how many trips you have left.

User Test Flow

During the User Test Flow exercise, I wrote the 6 steps that the app users need to perform from the entry point until reaching their goal of validating their ticket. This step is designed to make the next step easier and faster.

Storyboard

The most important task of the day was to fill in the Storyboard. The idea of the Storyboard is to sketch out an entire journey through the product with enough details what goes into the prototype. After the Storyboard, there should be no open questions about the concept, so that during the next day I can focus on prototyping. No brand new ideas should be added at this point (which is hard).I placed the user steps into the 8 cells and started drawing the concept screens. I spent 3 hours on the Storyboard, brainstormed different solutions and approaches. And at the end designed the whole 11 screens (instead of the expected 8). But some screens were very simple.

Ideate

Day 3 - Prototype

The goal of this day is to build a prototype that can validate the solution.

Wireframe Prototype

Since I already had the detailed Storyboard,  it took me  only about 1 hour to create a digital wireframe prototype in Figma.

High-Fidelity Prototype

After testing the flow with wireframes, I decided to create the highfidelity prototype and test it with real users.

Ideate

Day 4 - Test the prototype with users

The goal of the 4th day is to conduct the user testing of the prototype, collect the feedback and make a decision about the next steps about the product.

Interview

I drew all names of the participant on the whiteboard with the name of all interviewers and the list of features about which I wanted to receive the feedback. I interview everyone for 30minutes. I could not film the interviews for that I am very sorry. But from now on I will definitely will record them.

As for the interview process itself, I tweaked it a little bit. Instead notetaking immediately and recording pros/cons during the interview, I took notes and recorded important points. Then after the interview, I collected all notes together to create the combined stickers of pros and cons. On the red stickers, I wrote what users dont like and to improve it, on the green — what users liked, on the blue — general comments/insights.

One important lesson I learned - Interviews are hard and I definitely need bigger white board.

Possible Solution

A highly curated experience

Striving to create the process of using public transport more convenient and pleasant, through easier flow for finding the ideal bus ride. Virtual bus card and easy way to add more ticket rides to it.

Find ideal bus ride

Search your destination, set your current location. See all buses, choose which one is most convenient for you.

Check card and add more travels.

Choose how many tickets you want. Add more tickets to your bus card.

Possible problem solutions
01

Making the usage of public transport more reliable and simple

02

Accurate information about bus routes and estimate time between a bus stops

03

Saving time with easy buying tickets opportunity

04

Saves favorites for quick reference later

05

Gives users more flexibility to create specialized lists

06

Provides a source of reputable reviews from trusted friends and influencers

Day 5 - After the sprint

In the end of a design sprint is really the start of product or feature development, and the learning never stops. Once you get the hang of prioritizing and getting user feedback on the things you’ve shipped, you’ll be able to adjust the scope of any new iteration of your product, based on user needs.

Typography & Color

More Case Studies