Lime App Group Rides

Disclaimer: I am not an employee of Lime and this does not represent the official strategic direction of Lime.

Project Scope:

  • My Role: UX Design, research, product thinking
  • Tools: Sketch, Adobe XD
  • Timeline: Sep 2018 (2 Weeks)
  • Deliverables: Sketches, interactive XD prototype, research findings
  • Team: Just me, myself and I

Where it all started?

I recently used the Citi bikes in NYC. One night my wife and I were biking around Brooklyn and my phone died. At this point, we were almost 2.5 miles from our car and it was getting late. Since we couldn’t rent another bike from her phone, I ended up riding on the back of her bike the whole way back. You can guess that this option was not comfortable or safe but there was no way to rent another bike and we didn’t want to walk.

As I thought on this experience I felt like Lime riders may have a similar issue. During this case study, I wanted to explore a way to solve this problem.

The Problem

A feature allowing a Lime user to rent multiple scooters on one mobile phone is not currently available. Lime users have complained throughout app store reviews about the lack of this kind of feature.

The Challenge

Design a feature on the mobile Lime app for users to rent multiple scooters on a single phone.

My Approach

Initial Research

Before diving into any problem, it’s important to understand the users and the problem more deeply. To start my process, I wrote down some important questions to consider:

  • Is there clear data showing users really face this problem?
  • What are the implications of this potential problem?
  • What are use cases correlated with this problem?
  • How will solving this problem benefit the business?

Interviews

I interviewed 6 people that use Lime on a weekly basis. My goal was to learn about use cases surrounding this problem and why they might need this feature.

Discovered Use Cases:

A group of friends/family/co-workers want to go ride scooters together around the city...

  • but one friend’s phone is dead
  • but the payment info doesn’t work on one of the friend’s phones
  • but the data isn’t working on a friend's phone so they can’t download the app
  • but a family member didn't bring their phone

Implications of the problem:

From talking to users, I learned that most of them find other forms of transportation as a group if faced with the use cases listed above. Other forms of transportation included Uber, Lyft and public transportation.

App Reviews & Survey

In order to find more data, I went through app store reviews and found many people complaining about this lack of feature. I also found a survey conducted by Lime in San Francisco. The survey indicated that 10% of Lime customers use the service for recreation. Based on that information, my assumption is that recreational Lime riders travel in groups.

User Quotes (From the App Store):

“There is no way for one user to activate another's scooter... Why hasn't it been solved? What happens when someone's phone dies?”
“First problem, you can't actually rent two bikes from one account! What kind of business only sells one item per customer?! That is ridiculous.”

Persona Development

Based on my research and discovered use cases, I developed a persona who rides Lime scooters in groups recreationally.

Why solve this problem?

Solving this problem could help benefit the business and customer:

  • New Users - By focusing on recreational Lime riders as the target market for this project, Lime will be able to provide a better experience for new or potential Lime riders.
  • Product differentiation - Currently, other Lime competitors such as Bird & Spin do not allow users to rent multiple scooters on one phone.
  • Ease of use - Serving these specific edge cases would create a simple solution for Lime riders looking to ride in groups for recreation.

Ideate

I started my ideation process by sketching on a whiteboard. After brainstorming, I felt that visibility and user control were important heuristic evaluation principles that I needed to focus on while designing. I felt this way because a user renting 2-5 scooters will want to be able to view how many scooters they have rented and have the ability to end scooter rides at any time. I designed components to represent each rented scooter with the QR code provided.

Design Goals:

  • Focus on visibility to allow a Lime user to always know how many scooters they have rented
  • Focus on user control to allow the Lime user to be able to end a ride at anytime

I iterated a few times on the best way to design this component. As I iterated, I placed the component in the context of the screen to better understand how it interacted with the product.

I decided on the last component due to the limited screen real estate on the mobile app. The QR code is easy to access and large enough to read.

Things I considered:

  • How should users be notified about this new feature?
  • How many scooters should a user be able to rent?
  • Who is responsible if the scooter is damaged? Renter or rider?

Testing with users

To gather user feedback on the feature idea, I built out a prototype in Adobe XD and tested it with 5 users.

I had high hopes that the interaction of ending a scooter ride could be similar to deleting an app on an iPhone. Turns out users were confused and felt it took to many steps.

Issues:

  • Too many steps to end a ride
  • Users don't know which scooter is which when ending a ride

Iterate

To find a better solution, I did rapid sketching on paper. As I sketched out each flow, I wrote down the pros & cons of the design. I decided on option 3 for a few reasons:

  • Helps the users visualize the scooters they have rented
  • Allows for less clicking
  • Multiple scooters can be rented without taking over screen real estate

Option 1

Option 2

Option 3

To help users be aware of which scooter is which, I allowed the user to access the ringer ball to help find out which scooter to end.

Final Prototype

Lessons Learned:

  • Don't make design decisions without context. Try placing your components in the context of what you are designing for.
  • Iterate, iterate, iterate. Keep tweaking or adjusting until you discover the best design.

Next Project

Visual Design Collection