UX Designer, UX researcher
4 months
Mobile app design, user & market research, prototyping
Without an onboarding flow, CoinWa, a gamified financial literacy mobile app, was experiencing high user drop-off during testing. CoinWa is a Waterloo-based start-up and is in the pre-launch stage of their business journey.
Through extensive user research and iterative design, CoinWa promoted user retention with an effective, informative and user driven onboarding flow that optimizes for personalizing the app and segmenting users for increased growth potential.
Improvement in user completion of the onboarding flow after implementing the new design
Increase in Net Promoter Score through improved personalization
Reduction in design iteration time through organized component library and design system
CoinWa is successfully attracting the attention of potential users through their social media platforms. However, upon testing the app, most users are unable to complete tasks, navigate through the app, or leave generally underwhelmed.
Without effective onboarding to drive activation, most acquired users disengaged before reaching meaningful product use, limiting retention and revenue growth.

For competitive analysis, I studied Duolingo's approach to understand best practices in educational app design:
š Early engagement increases retention: Letting users experience core functionality reduces drop-off and builds immediate interest
š§© Progressive disclosure reduces cognitive load: Presenting one simple question or task at a time helps users stay focused and committed through onboarding
š® Gamification motivates behaviour: Incorporating progress bars, streaks, and small rewards during onboarding encourages users to complete the flow
šÆ Personalization increases relevance: Tailoring the user experience based on onboarding inputs (e.g., goals, skill level) enhances engagement and perceived value
š¬ Conversational tone improves approachability: Friendly language, playful visuals, and positive reinforcement make users feel safe to explore and learn
While having analyzed the existing designs and mapped out some of the potential changes, I thought it is best to get user input to measure current engagement, study user interactions and get feedback for the onboarding process. Thus, I organized CoinWa's previous designs (which were spread across three different software) and made a working prototype to prepare everything for user testing.

Screenshot from one of the usability study sessions (participant blurred for privacy)
"I have a relatively good knowledge of financial literacy and did not feel challenged by the lesson. The first lesson being so elementary makes me think that many of the beginning levels of the game will be redundant."
"Why can't I start at my level instead of at the beginning?"
"May skip or abandon future sessions"
"Skeptical about the app's long-term usefulness"

The Curious Beginner
Uses school-issued Chromebook for assignments
Uses Android phone for games and learning apps
"I want to learn about money in a way that's not boring or complicated."
Maya is a high-achieving Grade 10 IB student who thrives on structure and routine. While she's heard her parents discuss saving for university and understands money's importance, she lacks confidence in managing finances herself. She has a small allowance but hasn't developed the habit of tracking her spending. Her parents handle most financial matters, and their advice is limited to general statements about saving for the future. She's eager to learn but needs clear guidance on where to start. Given her demanding academic schedule, she values apps that are efficient and straightforward. She's motivated by goal-setting and seeks a learning experience that breaks down financial concepts into digestible pieces without overwhelming her.
Through user testing and research, we identified critical pain points that were impacting user engagement and retention.
Users found navigation difficult without a tutorial and needed guidance to understand the app structure.
Most users said that the level of the lesson was significantly below their current level of knowledge.
Users were unable to complete tasks and felt overwhelmed during their first app experience.
Users left the app feeling underwhelmed and disengaged before experiencing the core product value.
Reflecting on the insights from the usability studies and other research, I designed the intake quiz flow, and the app tutorial/run through to help new users with the app familiarization process.
For the intake quiz, it was important to create a powerful intake process that will assess the user's current level of financial literacy and place them in the appropriate level of learning on the app so as to prevent redundancy. During user testing, we found that users felt the first lesson was common knowledge and they did not feel like they learned anything new. The inability to skip the lesson was one of the pain points many testers experienced. Hence, I used diagramming to lay out the learning path, which helped me create the structure for the quiz and the algorithm through which it would distribute users across lessons matching their level.

Lessons flow diagram
Based on research insights we narrowed down the onboarding process to 3 mains components:
1. The tutorial of the app/app run-through
2. Questionnaire about user's goals for using the app (to help personalize the app's features to the user)
3. Intake quiz to determine user's current level for placement
The next challenge was to place these elements strategically in the app so that we achieve the goals of informing the users about the app's features and at the same time gathering enough information to help with goal setting and optimizing the app for individual users. As altogether, these elements can become time consuming, cumbersome and boring, by placing them incorrectly we could risk early drop off.
How might we structure the onboarding flow to maximize user engagement while minimizing cognitive overload?
How might we deliver the intake quiz and goal-setting questions in a way that feels like part of the user's journey, rather than a barrier to it?
To determine where best to place the intake quiz and app tutorial, I drew a user flow chart. After several iterations I decided that the following onboarding flow was ideal:

Onboarding flow
At first I felt that the app should follow the conventional structure of: sign up, questionnaire, and then app run-through, however, when running that prototype, the flow felt excessively long and disengaging. By playing around a bit (and consulting with one of the previous user study participants), I understood that the user should:

Intake quiz design examples
Above are some of the final designs from the onboarding process. The full flow can be seen in the video in the header.
Next, we needed to create the questions for the intake quiz which would determine which unit/lesson the user starts from. Considering the number and content of lessons at the time, we came up with 12 questions (4 questions/unit). I then created a distribution system that would place users in the appropriate unit based on their answers. This distribution system can be seen below:

Intake quiz assessment
While this system is specifically designed for the units in the MVP, a similar algorithm can be employed as new lessons are added.

Intake quiz questions, scoring, and distribution
Below are some examples of the quiz designs:

Intake quiz design