The Story

The reason for working on a portion or extension of Uber is that I realised that the app does not have the feature of booking cab for more than 6 people or has the option to book multiple cabs at a time. So I thought of creating a story with a User persona (Diganth) where the user who is a Bangalorean, is working at a MNC in New York. He recently got acknowledged at work for his outstanding performance in the team and is going to be awarded soon.


User wants to invite his family and friends for the award function and has already booked flight tickets. Now he has to book Uber cab for a total of 9 family members from home to airport.


Unfortunately as user is not in Bangalore, he has to book a car in Bangalore from New York itself as his family members are not tech savvy people.


Studied the current Uber app and other location sharing platforms including google maps geo tagging which updates the user about the cab/driver arrival to the pickup location. Social app like Snapchat have a bought a location sharing app called as Zenly which was primarily targeting location sharing, which helped me in understand the platform even more.


Due to the Uber’s rapid growth and being a avid user of the app, there was already plenty of data available to plan and design it. So I used this accurately to define the user behaviour and use cases of the app.

Without a clear understanding of what you need from a product, what problem it solves or for whom. Ultimately there’s no need of a product. Goal is to make sure that the app solved typical scheduled trip for large group of people in a clear and simple way. So I created few user behaviours and app use case.


Quick cab booking, when a user has to travel alone with friends & family to different destination. It's not a planned ride. These type of rides are expected and driven by user desire.

Planned Trip A

A similar scenario with the emergence of desire. The difference is in advance planning where the user booked the cab hours or days before often implies a view of the expected plan. Here the user plans in advance which includes friends, destination and the mode of transport.

Planned Trip B

This often starts and implied with a view of the expected plan. And the user is booking the cab for his friends of family from a remote destination.

Wireframing: Low-Fidelity Sketches

With a proper planning, I was able to confidently move into creating paper sketches for the app. I took the decision to focus more on the functionality and structure to keep it consistent with the current app., opting for low-fidelity wireframes with very little detail. Ultimately, I could add design elements later which are important for the users and the usability is clear and simple.


One major part in the app was to focus on personalisation and add the option for user to book cab for large number of people, multiple cabs with added destiny.

I planned by structure to create a visual design language which flows in sync with the current Uber app to create a simpler, easier and more structured way to book cabs for large numbers in a planned way. By keeping all these things in mind, aim was to build a design with is simple and clear hierarchy which users can learn and use.

User can start planning for a trip first by scheduling a time. After that user is prompted a screen which asks for the destination. Once the user has added the destination, he can choose the number of people for commute.

Based on the data (time, destination, number of people) the app pushes the user the most relevant mode of transport. As 9 members can’t be seated in one car, app suggests the user for a premium car (UberXL) which can seat 6 people and a regular Uber Go which can accommodate rest of the 3 people with all the luggage distributed among two cars.

Once all the info is collected, reminder messages will be sent to two or more people from the 9 member ground about the cab booking status. With this we removed the need of booking multiple cabs with multiple accounts as multiple cabs can’t be booking with single account.

You can see a prototype of this flow here. Stakeholders need to get a sense of how the product look and feels, so I created a visual prototype below.

Here’s a glimpse into the massive booking, which was arguably the most important and complex part of the app. So I put a lot of time & thoughts into it to get it right.

Landing Page


Add Destination


Who will be Riding?


Send Trip Details


Select your Ride!


Schedule a Ride


Ride Details


Change Capacity


Ride Confirmation


Loophole: Why doesn’t Uber have the feature of daily planned commute trips. Why should the user book a cab at the same time to same destination everyday, which is a waste of time and frustrating, in terms of arrival and planned trip

Thank you for checking my work!