RIDE SHARING APP

Role
Interface Design
Platforms
Mobile
Industry
Transportation
Year
2018

Design problem

Traditional on-demand bus services for rural areas were implemented for years. Customers called the reservation centre and buses arrived 1 hour later to pick them up. No online or mobile booking was available. Moreover, there was a lot of manual effort required to dispatch the ride request to the driver and vehicle.

Solution

The perfect driver application. Know where my possible customers are, when and where they want to go and conveniently transport passengers. A smart solution which does not distract the driver.

Approach

Understanding the problem

Before I went straight into the research phase, I had to take my time to understand the nature of the problem, which made me pick out the keywords in the issue. These Action words helped in understanding the kind of product and environment I was solving
Decentralize, Gridlock Cities. Urban Mobility Solution, Shuttle Service, Consumers, Consumer Locations, Public Transportation, Shared Economy, Request Rides, Accept Request.

Research

The purpose of this research was to understand the current situation, problems, constraints, people’s experiences, and opinions about public transportation. We used Lagos state, a state in Nigeria as our case study. Lagos State, identified is the biggest city in Nigeria with gridlocks, bad roads, and poor navigation system. It also has unmarked road networks.
I made extensive use of Qualitative Research to understand the problem, gain users' empathy, and develop personas to guide my storyboards, user journey, and wireframe. Below are the questions that I created for the research participants.

Persona

The results of the research provided me with an elaborate guide on what are the everyday challenges of the drivers. After gathering insights, I found fascinating ideas about their needs, wants, motivations, expectations, and current problems, which, as a result of the users' answers this helped me to create three personas.

User interview

Notes: Due to the instruction of the other interviewers, I was asked not to use their images, so I had to make use of just one of my interviewers.

Quotes directly from the users:

“I face a lot of extortion from the head group of my association ”

User Persona gotten from the quantitative research

Competitive Research

We paid close attention to the consumer market - Asia, Latin America and Europe. Next, we researched the different live products under each of these categories.Solutions: carpooling, ride-sharing, smart shuttles, free-floating cars and scooter sharing.

Competitiv Research across 3 different continent

User Journey

After brainstorming, researching, talking to people and having a better understanding of who I would be designing for, it was time to make use of all these pieces of information to find a solution. I categorised and prioritised the most common and most pressing pain points and would be highlighting them with the various ways they can be solved.

That been said it would be essential to highlight two critical scenarios which the bus driver will be operating on, the part that I will be looking at is the  on-demand service and pre-booking service

On-Demand Service

  1. Scenario 1 (For Group of Riders ): The driver is parked somewhere, at a point called A. Receives a request do you want to drive X number of people from B to C? Driver accepts. Now the app navigates the driver to B. When he arrives, the group of people gets up, and the driver pushes a button to start the trip Started. That means that people are in the car and the navigation can now show the ride to C. At C the driver presses trip Ends. Reduce the time it takes to onboard a user.
  2. Scenario 2 (For riders scattered along a route ): The driver picks up his app, and he enters his desired location in the morning, and when that is done, he begins to see markers(this represent the number of riders requesting for a bus ride at different intervals). He picks them up and as they enter using a QR code which is used to reconcile any payment for the driver which removes the headache of the driver bothering on the price and also continually monitoring the number individuals in his cars.

Pre-booking service

  1. Scenario 1 ( For Group of Riders outside the state):  If the riders is parked at a location he gets a request which is 24hrs earlier to the trip due to the fact the system as the ability to delegate rides to all the drivers and this will, with this in place these will give the driver an amp-full of time to be able to prepare for the trip and plan.

User flow

After a lot of consideration, I decided to focus on the driver to many riders which are the on-demand service (For passengers scattered along a route ). Creating a flow for the app allowed me to figure out each step of the users throughout the solutions.This flow is based on some assumption that the driver and the rider do have access to the internet neglecting any internet disruption.

user flows

Sketches

I created a sketch user flow that will enable the drive to be able to pick multiple numbers of passengers with the help of reducing the cognitive overload of passengers request. I then decided to itemize the request in the form of a list.

Wireframes

I had to design the screens to focus majorly on the functionality and giving it less thought process on the visual design.attention to the visual flow.

Wireframe

How the App  will work

The model is pretty simple. The Driver wakes up in the morning sets a specific location on the app, and the app begins to poll request from different riders within the area. The Driver sees all the request as a list not minding the names of the people because the most important thing for the Driver is to know the where, when and how long will it take to meet the Driver.

This approach assumes that there is a lot of clustered people within that location. While picking up each rider, there is a QR code which will be used for Driver to be to collect his money. The benefit of this model is to provide a solution where the Driver can make so much money without waiting for a specific group people (Pre Booking Service) to order the ride before he can leave the spot.

Visual Design

we are assuming that the driver as moved passed this stage of login into the app and also the on-boarding stage and I am going to focus only on the main screens.

Landing Page Overview

Driver Availability

The default screen right after the driver passes the credentials screen. This stage, the driver will have to tap on the button to show his currently online and the system sends out signals that his available.

Search

The flow of this screen is for the rider to input the destination which will determine the driver route for the entire trip. The rationale behind putting the search field close to the bottom is because of proper usability.
“49% of users who use just one hand typically hold their phone in a variety of position”.

Search Result

Drivers will need to quickly get the most recent destination or favourite destination to avoid retyping of the same address at all time.

Request

This screen slides in the moment request begin to come in at this point the Drive taps on the request and that shows him all the request.

Rider Pick Up

At this point, I was looking at what will be the best option for the Driver because while driving is not so concerned with map seeing all the request as a pin which will cause a whole lot of cognitive load. So I decided to put in a List View at this point the Driver top priority is to know the location (Where) and distance ( Time) with this all he has to do is to swipe to the right to accept the entire request.  I decided to add an info button at this point the Driver would like to know the specific details of the particular passenger the Driver will be picking up and also know how far is the time of arrival.

Wireframe APIs Documentation Exploration

Rider Details From Driver Perspective

 Granular detail of the rider and I decided to have  2 versions to compare which screen will be situated for the Driver — looking at
version-1. I removed any dots to make it each Driver this way every rider is equally important, which means he can drive straight down to pick up the rider. I mentioned it earlier that the cognitive load for the Driver is significant that why I removed all the pinpoints.

Unlike version-2  there are a lot of passengers scattered around that will not be favourable for the Driver. Another major thing to watch out for in this screen is the confirm button this will inform the Driver to confirm every passenger at the point of pick up.

Rider Details From Driver Perspective

 Granular detail of the rider and I decided to have  2 versions to compare which screen will be situated for the Driver — looking at version-1. I removed any dots to make it each Driver this way every rider is equally important, which means he can drive straight down to pick up the rider. I mentioned it earlier that the cognitive load for the Driver is significant that why I removed all the pinpoints. Unlike version-2  there are a lot of passengers scattered around that will not be favourable for the Driver. Another major thing to watch out for in this screen is the confirm button this will inform the Driver to confirm every passenger at the point of pick up.

Conclusion

What did Iearn?

Designing and researching the app has been imperative and rewarding experience thus far. Right from the beginning I had a major challenge how can I use my country transportation system to give a better perspective on how this app can work knowing fulling well that my country transportation system is really bad. This led me to deeper  research and I was able to come up with an experience  that can work within a grid lock city like nigeria.

Next Steps

  1. Measuring the task analysis of the Driver
  2. A/B Testing on how the app is performing
  3. A detailed Business Model with different scenarios
  4. To know how easy is it to accept a request
  5. How important is for the driver to know the price for each passengers

Takeaways

  1. The use of mind map to understand the user journey was helpful.
  2. No idea is less important; it’s all about the narratives. How well can you defend your idea.