I live in LA. I don’t own a car and I don’t plan to. In terms of apps that I use on a daily basis, Uber is my go-to. I use Uber anywhere from 1–4 times a day.
On any given Thursday night at UCLA, a group of 6–15 friends can often be seen meeting at an apartment to pregame — then calling several Ubers in order to go out in Santa Monica. While this isn’t a major inconvenience, it breaks up the crew, delays the night, can leave the initial financial burden on 1–2 people. It would just be a lot easier if everyone could leave and arrive at about the same time.
Let’s imagine scenarios where calling multiple cars at once is useful:
Use Case #1: Big group of college students pre-game before going to bars
Use Case #2: Creative Director or manager plans an off-site bonding activity
I started thinking about how this interaction might work. I wanted something that would fit seamlessly with the current interface. Something that wouldn’t be complicated to understand–something that felt native to the app already.
After this, more complicated questions arose. I had to think about what would happen after the two cars were called. How notifications would work, what options users would want, and what factors would be most important.
This led me to my next explorations. I wanted to keep Uber’s split fare feature the same as well as mimic it for the ownership transfer so there would be less of a learning curve for users.
Instead of a split screen view, the rider is able to swipe between cars in a horizontal motion. This way is less confusing for people to understand and keep organized. While the technical back end was not in the scope of this, I imagine this would help keep infrastructure similar as well.
I asked a few people at my co-working space to interact with the prototypes I had made and to give me feedback for improvement. The biggest pain point was discoverability. It wasn’t clear that they could swipe to switch between cars or that they could transfer ownership and request payment. With this feedback, I tweaked some things for the final iteration.