B2C Mobile App

Favorite locations

Enhancing control over favorite locations with redesigned features for user convenience
A cover with mockup which gives you whole concept

Introduction

Snapp! is known as the Uber of Iran with over 55 million users. The company is the largest and fastest growing internet company in the Middle East, a super app that offers many services. This case study is about  ride-hailing service which is the most used service with 3.8 million rides per day.

How did we do it?

Based available data, benchmarking and heuristic evaluation, we discovered current design problems and then designed ideas based on our findings and benchmarks. The result was tested by usability testing, so we developed the solution and observed the metrics for a smaller number of users and then reached 100%.

What did I do?

As a product designer, I helped our research team in Reviewing data, did a competitor analysis, ideated, and designed the final solution.

Problem statement

The favorite locations feature was added to the app
with the aim of reducing the average ride request
time from 112 seconds to 90 seconds. But based on
our data, it did not perform well to achieve the
intended goals, and this feature only reduced the
average ride request time by 8 seconds.

Our goal

We wanted to improve the design of favorite
locations to achieve a significant reduction in the
average time of ride request, aiming to meet the
initial target of 90 seconds. But how can we know
if we have reached our goal if we can’t measure it!?

Metrics: Increasing the use of Favorite locations feature by X%  Decreasing the average time of ride request from 108 seconds to 90 seconds or lower than

Data reviewing

First, we had to understand why many users are
not using it and why this feature is not working
as we expected; So by using Clarity and the help
of the data team, the researcher and I, we
came up with the followings:

Competitor analysis

I checked popular apps like Tapsi, Neshan, Uber, Lyft, Grab, Waze, Bolt etc to have a closer look on features and interactions of Saved places page.

Heuristic evaluation on current design

We reviewed the current design and based on our findings, specified where we needed to take action.

Framing all we got from our discovery journey

We held a meeting with the product and technical team and based on the findings and results obtained from the data, benchmarking and exploratory evaluation, we generally discussed the possible changes and improvements to ensure that the changes were within the project scope and schedule. We decided to make these changes to the snapp’s favorite locations:

Ideating solutions based on our findings

To find solutions for the problems we identified, we started brainstorming with the team and the product lead and categorized the ideas into four groups.

Bringing ideas to life

First iteration

Why this solution didn’t workout?

  • Due to technical limitations, it was not possible to perform drag and drop on this page, and we had to go one layer further by creating a reordering mode.
  • Since the favorite locations details contain relatively important actions and on the other hand the keyboard is supposed to open and and push the bottom sheet up, so it is better to change it to full page.

Second iteration

Why this solution didn’t workout?

  • Considering the recent situation of our country and the issues that have arisen in relation to Snapp, the use of pre-determined items may lead to PR problems.
  • Redesign will be confusing while they have already saved their work and home address.
  • Similarly, users may experience cognitive overload when they are unable to reset preset items to align with their current preferences.

How did we solve the challenges?

What did we finally do?

  • Empty state illustration replaced by new related one
  • Cards changed to list component
  • Based on data we use 9 icons for our frequent names like Home, Work etc. Also we use a general icon as a default icon
  • Details input is deleted
  • Address added as a text with edit option
  • The option “Show as shortcut” changed to “Off” mode
  • An reorder icon considered to change to rearranging mode
  • In reordering mode, we placed the reorder icon next to the card instead of action menu so in this mode users ar not able to have any actions a part from reordering
  • Users will be able to edit both name and location

Final overview of what we did

I've iteratively redesigned this flow, considering numerous possibilities and ensuring all corner cases are addressed and to facilitate a clear understanding for developers.

The prototype

You can see the prototype here.

The impact

At first, it was rolled out for two percent of users and we tested its results with usability, and after seeing the positive results of usability, it was rolled out to 100%. We have done a thorough evaluation of our metrics since our full launch. The results show significant improvements, especially in two key measures:

  • Increase the use of Favorite locations feature from 25% to 43%
  • Decreasing the average time from 110 seconds to 89 seconds of getting a ride in rides that use favorite locations

For confidentiality reasons, I have omitted the actual values for these metrics.

These positive outcomes collectively underscore the success of the  delete feature redesign and the arrangement feature of favorite locations, demonstrating its effectiveness in enhancing the user experience across various dimensions.

Reflection

What I Learned

Effective Communication and Collaboration:

Navigating challenges highlighted the significance
of effective communication and collaboration
among cross-functional teams. Transparent
communication fostered a shared understanding
of priorities and facilitated collective efforts to
overcome obstacles.

Next Steps

In planning for the future of this project, we've explored
additional enhancements that were postponed due
to limitations in time, technical requirements, and
available resources.These include:

  • Promoting the feature through ride request flow.
  • Adding the ability to manage favorite locations in the ride flow.

Last one is particularly challenging, as it must be
implemented in a way that does not affect or disrupt
ride timing.