MY ROLE IN THIS PROJECT
Ideation
Research
UX Design
UI Design
Research
UX Design
UI Design
The Challenge
The unique needs of our white label partners led us to review and redesign our apps' onboarding flow, in search of a flexible solution that can support various operational needs
The project tried to tackle the following challenges:
-Create scalable white label system
-Reduce as much as possible the amount of friction the user has in the onboarding process.
-Find an easy way for logged out users to re-enter their accounts
The Old Design
Main Pain Points
-Doesn’t support white label’s operational constraint in the authentication process (such as high phone-call prices, users with limited technological proficiency, etc.)
-Long and discouraging user sign up form - high drop off rate
-Visual overload, with several CTAs
-No option to skip the payment - high drop off rate
Existing Solutions / Example
Sign Up:
The common tendency is to break the Sign Up process into small and easy to complete tasks instead of asking for the full list of information details in one step.
Log In:
Some existing services ask the user to provide a mobile phone no. as an identifier, using the SMS code as the security validation system.
New Onboarding / Proposed Solution
When Logging In:
Facilitate the process of logging in.
Avoid sending the user out of the app in case of a login issues.
When Signing Up:
Simplify the Sign Up process.
Create a flexible solution.
Modernize the UI.
Present the user with challenging tasks only when needed
.
New Onboarding / Exploration
New Onboarding - Final Solution / High Fidelity
Dynamic Password / Mobile no.
Asking the user to input first his Identifier (in this case - mobile no.) allows us to check if he’s an existing user or a new one and to lead him to the relevant flow accordingly. This process provides both a passcode and an account verification system at the same time while having a single, simple CTA - “Get Started”.
New Onboarding / Overview
New Onboarding - Final Solution / High Fidelity
Dynamic Password / Identifying
After the user enters his phone number, he gets an SMS with a code to his phone.
In case the phone number is affiliated with an existing account:
After entering the code - the user is logged in.
Dynamic Password / Sign Up
In case the phone number is not affiliated with an existing account: After entering the code - the user will be asked to enter his first name and last name (due to technical issues, there is a need to get them separately) and in the following step his email address (for receipts).
Dynamic Password / Payment Setup
A wide range of payment methods are placed in 2 distinct sections:
1.Payment methods that are defined in the app.
2.Payment methods that are defined by an external component.
A Skip function is placed in the top right corner, making it clear and present but secondary to the payment
methods options.
Skip Payment Setup / Booking Flow
If the user skipped the payment setup stage at the sign up, a friendly reminder will pop up at the next booking session.The user will be obliged to add a payment method the moment he will want to book a ride, at the ride proposals screen
Skip Payment Setup / Booking Flow
The payment setup components will appear on top of the map environment, leaving the user in the context of his ride booking process.
