Summary - Redesigned user registration flow for a weight loss and nutrition advice app called Asken Diet.
What it is - Asken Diet is an app that helps its users better understand their diet & nutritional intake and get advice on how to hit their nutritional goals. I was tasked with redesigning the user registration flow to: A) increase the percentage of users that complete registration and B) make registration easier to get through and more informative.
How it works - Upon launching the app for the first time a new user will need to register with Asken Diet. To do this, they’ll need to provide their personal measurements, preferences, email address & password. And in order for Asken Diet to provide relevant advice and goal tracking for the user they will need to input and edit their weight, calorie and activity goals. After finishing these steps the user registration process is complete.
My role - Research, strategy, wireframing, UI/UX, prototyping, design, bug testing.
Where to get it - Download Asken Diet here
-Increase the percentage of users that complete the registration flow.
-Percentage of users completing registration flow.
% of users completing reg. flow (iOS & Android)
Balancing length of flow, required fields, and contextual health info
The original Asken Diet registration flow was long and suffered from a health information deficit. The goals section was far too unwieldy, goals couldn’t be edited before completing, and the health information upon which users would be making decisions was few and far between. I knew that I would be able to solve these problems individually. The difficulty came in balancing the solutions to these issues in a way that allowed us to achieve our goals.
I was able to reduce the number of steps in the flow by condensing the goals portion into one page; all while still retaining the same amount of required fields as the previous flow. This new Results page combines goal information for all goals and is designed in a scalable way as to allow for more goals to be added in the future. The Results page was also the perfect spot to include goal editing. Each goal can be edited separately, but the effects of those changes are reflected in the other goals automatically (ex. increasing your Calorie Intake Goal will automatically increase your Calorie Output Goal in order to retain your Net Balance Goal). The Results page also served as a welcome spot to include important contextual health information that would be beneficial to the user when editing goals. The interplay between these solutions made it possible to increase the percentage of users that complete the registration flow by twelve percent.
Old registration flow balance
New registration flow balance
Building my own Sketch symbols library was a good call.
I created and maintained Asken Diet’s Sketch files for both iOS and Android. This included organizing hundreds of standard and custom symbols. I was able to iterate very quickly by utilizing the overrides panel to choose different symbols I created and edit text on the fly. Instantaneously swapping out list items, pickers and text was especially helpful for this text heavy registration flow project. Without my own Sketch symbols library, shipping this redesign would’ve taken much longer.
It was a bummer not doing any user testing.
I was so excited to finally do some honest-to-god user testing for this project. I was ready to user test the original registration flow and watch how users actually worked through the process from start to finish. We were using Firebase + Google Tag Manager to track certain actions in the flow but I wanted to sit with users or record them actually using it to see how the Firebase data correlated with actions I witnessed firsthand. It was unfortunate to hear that, for a number of reasons, user testing was not a possibility and that I needed to rely on Firebase data when coming up with solutions. In the end this project was successful, seeing that we increased the percentage of users that complete the registration flow by 12%. I just can’t help but wonder if we could’ve gotten that percentage higher by taking the time to user test beforehand.