Racemappr is a mobile app that helps users to find running races based on location, connects them with like-minded people, and allows event organizers to easily promote their events.
I was asked to help optimize the user registration process. To use it as a tool for education, and setting expectations for when the users arrive in the app, and to reduce/avoid drop-off.
Two - three months.
The design approach included eight steps that covered both User Experience and Visual Design.
As part of the research phase, I conducted a competitor analysis and I discovered common UX practices in similar apps that were not being used on the Racemappr app.
I gathered a group of 13 runners and asked them to login into the app while taking notes and observing their behavior. This helped me notice areas of confusion and uncovered opportunities to improve the overall user experience. After they were logged into the app, I discussed potential changes and asked them a few questions such us:
1. What features do you find most valuable and why?
2. How satisfied are you with the number of sign-up screens?
3. How would you describe your overall experience?.
Based on the results from the interviews, I developed a number of hypothesis on how to update the registration process:
~ Use progressive profiling to allow user to build their profile overtime.
~ Provide links with information on why required fields are needed.
~ Greet users with introductory content that helps explain the app.Greet users with introductory content that helps explain the app.
Using the conclusions I reached based on the data collected, I designed a more consolidated login flow reflecting the recommendations for acting on those conclusions.
I sketched out the login flow and made changes to the language, actions and fields required.
I gathered a different group of people to experiment with the two different versions of the app. This helped me construct new hypothesis, and observed their behavior with both versions. Below are some of the testing notes I took:
Majority of people used log-in partners, namely Google and Apple because of perceived security.
Testers preffered the onbarding process with less steps to land on the app.
A few people mentioned that the CTA’s were not visible enough on the original version of the app.
Everyone tried to skip giving personal info (DOB, phone, etc).
Everyone was ok with sharing localization.
With the new data collected from the A/B testing, I applied the feedback which further enhanced the user experience through the login process. The complete prototype is here
