A new Identification scanning flow that addresses high drop-offs resulted from our current Driver License scanning flow and accommodates market requirements.
A project for Lime’s mobile app
My work: Designed the whole ID scanning flow and planned for the future roadmap.
Team: Core Product Team.
Current Driver License scanning has high dropoff and only accepts limited forms of identity.
Understand the Problem
Why does the product have those problems?
Today, we have a basic US-style driver’s license scan using Google Vision. We did some user testing and data analysis, and found out that this approach has a number of problems as it does not:
- Create a seamless UX because of the quality of scanning tech and the user flow.
- Work for people without a US-style DL
- Enable all the government need.
What do we want to achieve through the ID scanning?
- We fulfill base requirements for all governments today and in the next 3 months
- We create base ID scan modules that work across all Lime products.
How are we going to solve the problem?
We will build two in-app modules:
- Photo-based ID scanning for multiple IDs powered by Microblink
- Manual ID entry.
High level user flow
Based on the technology constraints and the design goal, we would like to invest design resources in the photo scanning screen and to see how we can craft a smooth UX.
1. Testing the scanning flow
The main purpose of this user testing is to find out if:
- Users can pass the ID scanning smoothly.
- Users can discover the entry of other ID types.
- Dropdown list oftentimes works but needs to be more obvious.
- Horizontal scroll menu and slideshow diminishes the discoverability.
- Using a watermark to educate users works but need to be more specific.
Comments from engineers:
- The technology can work seamlessly without specifying ID types.
- Have a separate ID list would be a scalable solution on eng side.
- Have a dedicated area on the screen for scanning.
- The watermark is placed according to the best scanning distance and size.
- Highlight the part needs to be scanned by text and symbol.
- A more obvious drop-down list entry.
2. Testing the manual entry flow
The main purpose of this user testing is to find out:
- how users are going to react when the scan failed.
- if users can discover the manual entry option.
- Users will be actively looking for other options if the scan failed.
- a single CTA button has the highest discoverability.
Comments engineers and the GR team:
- Manual entry is not always a legit option because of the technology we will be using.
- Place friction in the UX for discovering manual entry intentionally.
- Still, make it an obvious option when the scan fails to cut down drop-offs.
What’s the outcome of the design(In progress)?
Target metric outcome
We would now like to start quantifying the cost of our gov-tech features, i.e. the impact on trips (via user drop off) this feature will have. Thus, we also need to gather the data to show the %trips impact our feature will have in a market.
- ID scan works for __% of users
- We manage to convert __% through the funnel for Lime-S