Ezata mobile app
Overview
Ezata is an app servicing transporation needs for commuters in Addis Ababa. The founder reached to me concerning a problem they had that needed to be solved and I will explain that here.
This is a case of an already existing ride-hailing app, that needs this problem solved in order to be able to cater to a wider range of passengers in Addis Ababa.
Problem
Generally, passengers can order rides and then have a driver come pick them up and take them to their destination. But they got feedback from users regarding a lot of cases where a driver picks up a passenger along the street (no prior booking) and then they want to sync the trip with the app for multiple reasons which could either be safety, fair pricing, or no knowledge of destination location.
Understand
the users
I already had knowledge of the kind of people we are dealing with from speaking to the founder and data from users in that area and I put together this persona as a north star to the design solutions
What to do?
How can we cater to both passenger types and the driver? Because the driver needs to be able to sync his rides with his app for fair pricing and safety. And then some of passengers doesn't want to go through any complex process, some don't mind, but both wants to get to their destination and enjoy the safety benefits of having the ride synced on the app.
What ever it is, it needs to be seamless and straightforward.
Design
I came up with a solution that accommodates for the most likely scenarios based on insights & the type of people we are dealing with, and also provides flexibility for other scenarios.
Initiating a ride
Because most times only the driver knows the address, I’m displaying manual input as the primary & default method to present drivers with the most likely & straight forward option while still offering QR scan as a secondary option that will work well in the event that the user knows the address, and can generate the QR code from their app.
Ensuring Safety
For unregistered phone numbers, driver verifies them by requesting an OTP to their phone number and once verified, the number is attached to that trip for safety.
For registered phone numbers, the system recognizes the existing user and prompts them to verify through the app, with the option to use OTP via SMS or call if preferred. Upon successful verification, the trip can begin
Additionally, this phone number verification process provides a valuable opportunity to encourage unregistered users to download the app and become registered users, enhancing user acquisition.
Key Takeways
Here are some takeaways to note:
Collaborating closely with devs was essential in understanding the technical constraints and capabilities of the system and arriving at the easiest and most direct logic for the user
Recognizing the specific transportation habits and needs in Addis Ababa was very important because it is not the usual.
It was important to ensure that the solution integrated seamlessly into the existing app flow, enhancing usability without disrupting the user experience.
+1 (682) 325-8032