Password protected

All case studies share one password — please contact me for access.

Password protected

All case studies share one password — please contact me for access.

Back
Home
Home
Home
Home

Building an NCLEX exam prep app from MVP to ExamReady’s flagship product

Role

Sole Product Designer

Sole Product Designer

Platform

iOS (iPhone, iPad)

iOS (iPhone, iPad)

Timeline

2025–2026

2025–2026

ExamReady is a B2C product line of eight mobile apps for high-stakes exam prep across four domains: Medical, Driving, Citizenship, and Military. I designed its first product, the NCLEX exam prep app, then the rest of the line, all on a design system I built.

ExamReady is a B2C product line of eight mobile apps for high-stakes exam prep across four domains: Medical, Driving, Citizenship, and Military. I designed its first product, the NCLEX exam prep app, then the rest of the line, all on a design system I built.

This case study focuses on the NCLEX app, which helps nursing candidates prepare for the U.S. nursing licensure exam. Here, I had the broadest design scope across the line: discovery, defining the MVP, new features, A/B testing, and post-launch optimization.

This case study focuses on the NCLEX app, which helps nursing candidates prepare for the U.S. nursing licensure exam. Here, I had the broadest design scope across the line: discovery, defining the MVP, new features, A/B testing, and post-launch optimization.

+43%

+43%

+43%

purchase conversion

Trial-first paywall: +37% ARPU and +49% trial starts in an A/B test.

71% vs. 46%

71% vs. 46%

71% vs. 46%

D14 retention

Game Mode: paying users who played vs. those who didn’t.

1–2 days

1–2 days

1–2 days

design time for a new app

Design system: down from ~2 weeks, one library for eight apps.

The challenge

NCLEX is a computer-adaptive nursing licensure exam built around different question formats, from single-answer questions to complex, connected clinical case studies.

To stand out among competitors, convert users, and retain them, the app had to be:

Genuinely useful

The exam tests clinical judgment, not memorized facts. Candidates needed practice in every topic and question type, with clear explanations.

Worth practicing daily

There’s too much material to learn in a few sittings. Candidates needed a daily study habit and a reason to keep coming back.

Clear about readiness

Not knowing where you stand is stressful, especially when a retake costs time and money. Candidates needed a clear picture of their progress.

Building the MVP

Our team researched the exam: who takes it, its format, question types, and topics. I audited 23 competitor apps for common patterns and friction points to avoid. Then I mapped user context, needs, pain points, and aha moments in onboarding and the product.

Our team researched the exam: who takes it, its format, question types, and topics. I audited 23 competitor apps for common patterns and friction points to avoid. Then I mapped user context, needs, pain points, and aha moments in onboarding and the product.

With the PM and engineering, we prioritized the MVP, balancing competitor patterns, build effort, and what the core experience needed. Once the scope was defined, I translated it into the product architecture, core flows, and wireframes.

With the PM and engineering, we prioritized the MVP, balancing competitor patterns, build effort, and what the core experience needed. Once the scope was defined, I translated it into the product architecture, core flows, and wireframes.

MVP product architecture

MVP product architecture

What we left out

With no user research before launch, we aimed to ship fast and learn from real data. To validate the core practice loop first, we left out a readiness score, a question of the day, clinical case studies, referrals, and a full exam simulation. Several came back in later releases.

Activation

Defining the first aha moments

To activate new users, I chose two moments to show the product’s value: a personal study plan and the first quiz.

From setup to study plan

Five setup questions (exam, date, weak topics, daily time, and when to study) led to a personal study plan: a projected path to readiness and the features to get there. Having invested in their answers, users would feel the app was built for them and be more willing to commit at the paywall.

Research insight:

With a lot of material and limited time, many users didn’t know where to start or how to prepare. They wanted a plan built around their level and schedule.

Success metrics:

Onboarding completion, step drop-off, and paywall-to-trial conversion.

Onboarding setup

Onboarding setup

From first quiz to daily practice

I made the Quick 10 Quiz the main action on the Study home screen: exam-style questions with explained answers. Matching the ten-question free limit, it let free users reach the results, with every mistake ready to revisit. I expected a first session that felt like progress to bring them back the next day, and the quiz to become a daily practice for busy days.

Research insight:

For users short on time, even 15–20 minutes had to feel worthwhile. They wanted to see weak spots and felt they were learning when explanations prevented repeat mistakes.

Success metrics:

First-quiz completion rate on install day and D1 retention of users who finished it vs. those who didn’t.

Quick 10 Quiz: question, explanation, and results

Quick 10 Quiz: question, explanation, and results

Revenue

Balancing conversion and long-term value

To turn free users into subscribers, I worked on where they met the offer and how it was framed.

Where users met the offer

Free users got ten questions in any mode. In longer quizzes, I proposed a trial offer right after question ten, betting that users partway through a quiz would start a trial to finish it. After the limit, any quiz opened the paywall. It also appeared at the end of onboarding, in banners, and in its own tab.

Success metrics:

Trial starts from the offer after question ten and their trial-to-paid conversion, compared with other entry points.

Trial offer after question ten

Trial offer after question ten

Premium banner

Premium banner

Leading with the trial

Like most competitors, the MVP paywall offered an annual plan, preselected, and a monthly plan with a free trial. Yet most users closed it without buying either.

Data insight:

The exam dates users entered in onboarding showed they typically had only a few months to prepare. For many, a full year was more than they needed.

We tested a bolder version: only the monthly plan with its free trial up front, and the annual plan one tap away in a bottom sheet. The hypothesis was that one free-to-start option, with nothing to compare, would bring more trial starts and, in the end, more purchases. We expected losing some annual subscriptions to be a small trade-off.

I designed the variant with discount and Limited Time Offer labels.

Winner

Winner

A · MVP paywall

Annual plan preselected

B · Trial-first paywall

Winner

Trial alone, all plans one tap away

MVP paywall

Trial-first paywall

A/B test · Trial-first paywall

Leading with the trial turned more users into buyers

+49%

trial starts

+43%

purchase conversion

+37%

ARPU

Bringing the annual plan back

The trial-first test won on conversion but carried a long-term cost: with the annual plan out of sight, revenue from it fell by about 80%.

Data insight:

Users stayed about 2.2 months on average, but annual subscribers paid for a full year up front. Even a small rise in the annual share could noticeably lift LTV.

So we brought the annual plan back to the main screen, preselected next to the trial, but not in its MVP form. I made the monthly price the main number on both plans so the annual savings stood out, and added a discount label, expecting more annual sign-ups.

Side-by-side plans

Side-by-side plans

Paywall update · Side-by-side plans

Making the annual plan’s value clear led more buyers to choose it

2.6×

annual share, from 5% to 13%

≈ +$5 LTV

per subscriber, projected over 360 days

The effect held for months, and this version became the main paywall.

Paywall update · Side-by-side plans

Making the annual plan’s value clear led more buyers to choose it

2.6×

annual share, from 5% to 13%

≈ +$5 LTV

per subscriber, projected over 360 days

The effect held through the following months, and this version became the main paywall.

Retention

Giving users reasons to come back

To bring users back, we focused on two things: learning that made every session worth the time, and mechanics that made returning rewarding.

The practice loop

Four quiz modes formed one practice loop: Random Mix for broad practice, Missed Questions to work through mistakes, Saved Questions to revisit what mattered most, and Mastered Questions to reinforce strengths. Each mode worked across all topics or within one.

The Review Questions tab collected every answered question, sorted by result and searchable by keyword. After we saw how often users searched, I added topic filters.

Research insight:

Afraid of forgetting something on exam day, users wanted to work through their weak spots until they’d mastered them.

Success metrics:

Percentage of quizzes taken in each mode, weekly Review use, and D7 retention of users who practice on their own answers vs. only Random Mix.

Quiz modes

Quiz modes

Review Questions tab

Review Questions tab

Seeing progress

The Stats tab showed progress overall and by topic: questions answered and accuracy. I expected the topic breakdown to show users what to practice next and keep them coming back to close the gaps.

Later, we added a readiness score: a single number showing how close users were to being exam-ready, giving them a sense of control.

Research insight:

Without a clear picture of progress, users couldn’t tell which topics needed work or whether they were ready to book the exam, which left them anxious.

Success metrics:

Weekly Stats use, topic quizzes started after viewing Stats, and D30 retention of users who check Stats vs. those who don’t.

Stats: Readiness Score and performance by topic

Stats: Readiness Score and performance by topic

Rebuilding the streak

The MVP streak was a simple weekly tracker. Its data revealed a threshold: for paying users without a streak, retention held steady through day five, then dropped sharply, to less than half that of users who reached a five-day streak. Yet only 54% of users who started a streak kept it going the next day, and the average lasted four days, just short of that threshold.

I hypothesized that early milestones and a one-question daily minimum would help more users get past the first few days and build a lasting learning habit.

Early wins, then long-term goals. The first milestones were close together: day 1 celebrated the start, day 3 sat just before our four-day average, and day 7 pulled users past it. Later ones at 14, 30, 60, and 90 each brought a new flame.

Early wins, then long-term goals. The first milestones were close together: day 1 celebrated the start, day 3 sat just before our four-day average, and day 7 pulled users past it. Later ones at 14, 30, 60, and 90 each brought a new flame.

A smaller daily step. One answer to the Question of the Day was enough, so even a busy day didn’t break the habit.

A smaller daily step. One answer to the Question of the Day was enough, so even a busy day didn’t break the habit.

A nudge for every streak state. Each state had its own message: start a streak, keep it alive, or begin again. The button opened a Quick 10 Quiz: the first answer saved the streak, the rest made it real practice.

A nudge for every streak state. Each state had its own message: start a streak, keep it alive, or begin again. The button opened a Quick 10 Quiz: the first answer saved the streak, the rest made it real practice.

Research insight:

High-retention learning apps build the daily habit on early wins and a visible next goal, so users always had something within reach.

Reaching a milestone

Reaching a milestone

Streak update · Milestones

More users kept streaks going, and the average more than doubled

MVP → redesign · users who started a streak

54% → 73%

reached a 2-day streak

28% → 49%

reached a 5-day streak

4 → 9 days

average streak length

1.75× more users reached five days, past which retention was over twice as high.

Milestones from day 1 to 90

Milestones from day 1 to 90

Streak nudges: start, keep, restart

Streak nudges: start, keep, restart

Customer development

Six months after launch, our PM ran an Intercom survey to find users’ top pains. It confirmed the pains from our initial research and showed what users needed next.

The findings moved clinical case studies up the roadmap and shaped how we talked about Cheat Sheets, as a way to ease exam anxiety.

192 respondents, mostly active subscribers · Jul–Sep 2025

What held users back

Top pains, by number of mentions

Exam anxiety

64

Cost

60

Lack of time

46

Hard-to-retain material

45

3.7 times a week

users meant to study but put it off, mostly because of time, fatigue, low motivation, or family

What users needed

Most requested

01

Clinical case studies in the Next Gen NCLEX format

02

More questions

03

A real exam simulation

What helped them study

Structured cheat sheets

Structured cheat sheets

Clear explanations

Clear explanations

Practice in the exam format

Practice in the exam format

Tracking progress

Tracking progress

Next Gen NCLEX case studies

Case studies are the hardest format on the NCLEX: a clinical scenario followed by six connected questions. We expected practice in this format to give users a reason to subscribe and stay.

On a computer, the exam shows the scenario, questions, and patient data side by side. On a phone, they compete for space, and in competitor apps, case studies were hard to follow. I collapsed the scenario above the question and put patient data in a bottom sheet, so users could check it without losing their place.

Research insight:

Case studies were users’ top request in our survey.

Success metrics:

Trials and purchases from free users who tap a case study, completion rate, and subscription renewal vs. users who don’t open them.

Case Studies announcement

Case Studies announcement

Answering a case

Answering a case

Cheat Sheets

Instead of selling cheat sheets separately, we bundled them into the subscription: a cheap standalone pack could have cannibalized it, especially among users who came from cheat sheet ads. We positioned them as quick relief from exam anxiety: short refreshers on the hardest topics.

I turned the content manager’s PDFs into a new category on the Study screen: a row of cards, a full list, and a full-screen viewer with zoom, available offline.

On the paywall, I presented cheat sheets as a gift with the subscription, and a modal after checkout pointed new users straight to them, so they got the promised gift right away. I expected seeing this value early in the trial to help more trials convert.

Research insight:

Exam anxiety was users’ top pain in our survey, and structured cheat sheets were among the study aids they named.

Cheat Sheets modal after checkout

Cheat Sheets modal after checkout

Cheat Sheets modal after checkout

The full list of cheat sheets

The full list of cheat sheets

A/B test · Cheat Sheets modal after checkout

Pointing new users to Cheat Sheets turned more trials into subscriptions

Users saw the modal after checkout or didn’t. The gift on the paywall was the same for both groups.

+40%

cheat sheet downloads

+11%

trial-to-paid conversion

+13%

ARPU

The effect held through the following months.

Usage

45%

of paying users opened Cheat Sheets, 8–9 times each on average

Compared with paying users who didn’t open them

Users of Cheat Sheets studied more and stayed longer

Sessions

3.7×

Session length

+23%

Time in the app

4.6×

Quizzes started and finished

1.5–2×

Subscription renewal

31.7% vs. 27.1%

D7 retention

~8×

Game Mode

Before building the game, we tested demand cheaply: a game-style ad creative and a game quiz I designed for our web funnel. Both performed well, so we brought it into the app.

We expected the game to make practice more engaging and bring users back even on days they’d otherwise skip. No competitor had anything like it.

I designed it to feel like a real game: three lives, an endless run of questions, a point for every correct answer, and a personal record to beat, with animations for milestones and new records. It kept the look of the best-performing game ad, so users from that ad or the web funnel already knew it.

Research insight:

Users put off studying 3.7 times a week, mostly because they felt tired or unmotivated. Starting had to feel like a fun challenge, not another task.

Game Mode banner

Game Mode banner

A Game Mode run

A Game Mode run

Usage

21%

of daily active users played

Compared with paying users who didn’t play

Players stayed longer, and the gap kept growing

91% vs. 76%

D1 retention

91% vs. 76%

71% vs. 46%

D14 retention

71% vs. 46%

Referral

Turning shares into referrals

To add a growth channel beyond paid acquisition, I designed ways for users to share the app, then turned those shares into referrals.

Sharing at the right moments

I mapped the moments when users might want to share: quiz results, cheat sheets, streaks, and Settings. At these moments, I expected users to feel the app helping them and want to pass it on.

Each moment got its own message with an app link, plus a branded image where it fit. Quiz result messages even adapted to the score. Cheat sheets could be shared only as a preview, since full ones came with the subscription. If users took a screenshot of a cheat sheet or streak, the app offered a branded image with a link instead.

Research insight:

Candidates often prepared alongside classmates or colleagues taking the same exam, so they had people to share materials and progress with.

Tailored share messages: a cheat sheet, all cheat sheets, a streak, and quiz results by score

Tailored share messages: a cheat sheet, all cheat sheets, a streak, and quiz results by score

Shares · Dec 2025 – Mar 2026

Cheat sheets led sharing by far

5,148

cheat sheets

506

quiz results

185

from Settings

56

milestones

Cheat sheet shares came from 974 users, about five each.

Inviting friends with a gift

Later, we launched a referral MVP. Every share point became a referral point: each message gained one line, “Get 7 free days of full access with my link — instead of the usual 3.” We expected the longer trial to give friends a reason to install.

I designed two invite points: a Settings banner and a modal after quiz scores of 60%+, when users were likely to feel good about their progress. Both framed the invite as a gift, so sharing felt like helping, not advertising.

For invited friends, an onboarding screen confirmed the gift, and the paywall delivered it: a 7-day trial on both plans.

Data insight:

Users shared cheat sheets far more than their achievements. They passed on what helped them study, and the app itself was exactly that kind of help.

Success metrics:

Banner and modal share rate, invite-to-install rate, and invited users’ onboarding completion, trial starts, and trial-to-paid conversion vs. other new users.

New referral points: the Settings banner and a modal after a strong quiz result

New referral points: the Settings banner and a modal after a strong quiz result

The invited friend’s path: the invite, a gift screen added to onboarding, and an adapted paywall

The invited friend’s path: the invite, a gift screen added to onboarding, and an adapted paywall

Design system

Scaling to eight apps

After the NCLEX app, my work expanded to the rest of the line.

When we built CDL Prep, the second app, it became clear more exams would follow. It took about two weeks to design in a separate file, and keeping two files in sync took more and more time. So I built a shared design system and moved both apps onto it. The next six apps used it from the start, consistent across the line.

The ExamReady line: eight apps on one system

The ExamReady line: eight apps on one system

The system included entire screens, adjusted for each exam. When an exam needed something new, I added a component or variant, so nothing lived outside the system.

A screen as a component: the base home screen and its properties, with features toggled on per app

A screen as a component: the base home screen and its properties, with features toggled on per app

With tokens, every app came in light and dark themes, on iPhone and iPad. Changing an app’s brand colors, theme, or device took one switch in Figma. I documented the foundations so engineers could rely on the same rules.

Design tokens: colors, sizes, and type, with modes for each theme, device, and domain

Design tokens: colors, sizes, and type, with modes for each theme, device, and domain

Speed and scale

A new app in days, not weeks

~2 weeks → 1–2 days

~2 weeks → 1–2 days

design time for a new app

159 components

159 components

in the design system, from buttons to full screens

Key learnings

01
Watch what a win costs

Our trial-first paywall lifted conversion but cut annual plans. Users prepared for only a few months, so one annual payment earned more than monthly ones. A conversion win can hide a loss elsewhere, so it needs a check on long-term revenue.

Our trial-first paywall lifted conversion but cut annual plans. Users prepared for only a few months, so one annual payment earned more than monthly ones. A conversion win can hide a loss elsewhere, so it needs a check on long-term revenue.

02
Design for the day users actually have

Users studied when they could, often tired, between work and family. Short cheat sheets, a quick quiz, one question to keep a streak, and practice that felt like a game kept them coming back. How people feel when they open an app matters as much as what they need from it.

Users studied when they could, often tired, between work and family. Short cheat sheets, a quick quiz, one question to keep a streak, and practice that felt like a game kept them coming back. How people feel when they open an app matters as much as what they need from it.

03
Prove demand before building

Game Mode proved itself in an ad creative and a web funnel before we built it, and in the app, players stayed longer than those who didn’t play. Testing first costs far less than building a feature nobody uses, especially when no competitor has validated the idea.

Game Mode proved itself in an ad creative and a web funnel before we built it, and in the app, players stayed longer than those who didn’t play. Testing first costs far less than building a feature nobody uses, especially when no competitor has validated the idea.

04
Check assumptions with users

Without resources for user research before launch, we relied on deep desk research. A survey later confirmed much of it and revealed what it couldn’t. Desk research can start a product, but data and user research show where to take it.

Without resources for user research before launch, we relied on deep desk research. A survey later confirmed much of it and revealed what it couldn’t. Desk research can start a product, but data and user research show where to take it.

What I’d do next

Talk to users in depth

Our survey showed what users wanted. In-depth interviews would show why, so we could solve the need behind each request, not just the request. Doing both regularly would keep us building what users find worth paying for.

Validate a full exam simulation

One of users’ top three requests, not built yet because it’s costly. A practice run under real exam conditions could ease exam anxiety, users’ top pain, and show how ready they are. A fake door test could check that demand first.

Measure the referral MVP

I’d compare invited users with those from paid ads on conversion and retention, to see whether referrals are worth investing in. Then I’d A/B test a reward for sharers to check if it pays for itself.

Next case study