Companion Apple Watch app for Uber
Introduction
Background
Uber, a pioneering transportation network company, offers seamless urban mobility through its user-friendly mobile app. With a focus on convenience, the app allows users to request rides, track their driver's location, and seamlessly pay for services. Real-time maps enable precise pickup and drop-off locations, while the rating system ensures quality service. Advanced features like upfront pricing and ride-sharing options enhance affordability and sustainability. Uber's app also offers additional services, such as food delivery and electric bike rentals. With its intuitive design, real-time updates, and diverse services, Uber's mobile app revolutionizes how people navigate and experience urban transportation.
Objective
The goal is to take advantage of the most popular wearable device, the Apple watch and the new widgets feature in watchos 10 to create an app that would allow users to use the functionality of the Uber mobile app without ever opening the phone. Since the Apple watch has much smaller dimensions compared to a phone, the primary goal while creating a design solution would be to create a compact UI with maximum functionality.
My Process
User Research
Key questions & answers that aided the design solution
What is the target audience for the feature?
The target audience for this app is people in their 20s and 30s who use Uber frequently to travel and have the Apple Watch as an accessory.
What aspect of using Uber does the user want on the go?
Users prefer to book cabs to saved locations and track updated on their ride on the go.
What are the users needs and goals?
The user’s goals are to complete repeated interactions like booking a ride to a saved location with ease and minimal friction. Since the user already has the watch on their hand, a few clicks can simply get the task accomplished.
Target audience & Personas
Based on the target audience of regular Uber users who own an Apple Watch and the interviews and surveys conducted during primary research, I created the three following personas:
User Research Results
Users travel to saved destination 70% of the time
8 out 10 users reported that their regular travel is always to saved destination. They travel to unsaved locations like restaurants usually irregularly like over the weekends.
80% of users pay after the ride using digital payment apps like Phonepay or GooglePay
8 out of 10 participants reported that they generally pay for rides after the fact with digital payment apps. This allows for the assumption that users would use their phone most of the times to complete payments
Observations and analysis
Sessions were observed and scored on different metrics. While most users were able to accomplish the tasks, several users faced issues. The insights dictated further iterations to cater to various pain points.
Assumptions
Users already have the Uber app installed
Since the watch app is a companion app, users would have to have the Uber mobile app installed on their phones, signed in.
Users have their target destination saved in their mobile app
Since the Apple Watch has very low real estate and small dimensions, typing is a hassle on it. Thus users would have to chose from their saved location added by them on the mobile app.
Users have their payment mode set in the mobile app
Uber offers both pre-payment and post-payment services. In case of pre-payment or post-payment, users can use their existing cards or Uber Cash or chose other to switch to the mobile app to complete the payment.
Users use their watch for other tasks
It is assumed that owners of the apple watch use it for many tasks like recording fitness, answer calls, glance at incoming notifications, etc. Thus they are familiar with interactions like using the scroll wheel and expecting data on scroll.
Ideation
Quick Brainstorming
I mean...
It will have the ability to book rides to saved locations
Ok, but why?
Because users typically traveling frequently to saved locations have all the presets like location and payment already configured. They simply need to choose the destination and click on book.
But
Users would need to use the mobile app to travel to unsaved locations, conduct pre/post ride payment. Users cannot completely rely on the watch app for complete functionality.
Therefore
The watch app will be a companion app that users who travel frequently to saved locations can use. IT will allow those users to select their destination, book their ride and view the ride’s status at a glance.
Scenario
It is 8:30 in the morning and Jeff needs to go to the office. His office location is already saved, hence he doesn’t need to type it. He opens the Uber app on his watch. On the home-screen he can see suggested locations as in the mobile app. He clicks on his office location saved as “Work”. After a few seconds, he is informed that Uber is searching for a cab driver. After two minutes, his watch buzzes and gives him a notification that a rider has accepted his ride and would be arriving in 2 minutes. The widget on his watch shows the progress of the rider and gives an ETA. Jeff walks from his house to his society gate in the meantime. Jeff gets his OTP on the watch as a notification when the driver arrives at Jeff’s location. When Jeff sits in the cab he scrolls down to view the OTP in his notifications and informs the rider. The ride begins. In the middle of the ride, Jeff swipes up to view the Uber widget which shows him the progress of the journey and ETA to his office. When he arrives at the office, he gets a notification from Uber to complete his payment. He takes his phone out of his pocket and opens GooglePay to pay the rider. He scans the QR code on the backside of the driver’s seat and completes the payment. Jeff then gets out of the car and goes to his office.
User Flow
The user flow prioritizes performing repeated actions from the mobile on the watch. Since it is a companion app, functionality would be restricted thus the user can perform repetitive tasks like booking a cab for a saved location and paying with existing methods.
Design Solution
Initial Wireframes (Key screens)
Low-fidelity Task Flow
‍To create the wireframes, I followed the watchOS guidelines for app screens as well as widgets. Using the wireframe stage, I illustrated the following task flow in detail.
High Fidelity Prototype
Open the figma link to use the prototype yourself.
Final Design
The final high fidelity design was created based on the general UI and branding of the Uber mobile app and watchOS guidelines to maintain the brand identity and create a familiar UI for users.
More options in video conference customization and sharing
Users can directly share video conference links on other platforms like slack to share with their coworkers for a seamless process of joining meets.
Learning
Learnings
This was my first project working on an Apple Watch app and creating a companion app. The fundamental features which a companion app should and can’t have was a learning step for me. Working with such a small screen was a challenge in itself, since I had to create a very compact UI without compromising on functionality.
Future Scope
Apple is trying to revitalize the Apple Watch with the new watchOS10. Their hope is that many companies would make apps for the Apple Watch considering the new features and UI elements. I feel that the Apple Watch is the most underrated tech having real world benefits.

Post-launch data drives the iterations of any application and thus depending on that data changes should be made. Additionally, Uber will have to think about every new feature being made for mobile from the perspective of watchOS as well, since if the watch app is neglected, user traction will fall.
Other Projects
Splitwise
Google Calendar
Hashnode