Learvo
Product designer (intern) at an ed-tech startup turning student notes into quizzes, flashcards, summaries, and mnemonics.
Oct 2025 – Present · 8 min read
TL;DR
- Problem
- New users landed on an empty dashboard, and returning users hit a nav that changed from page to page.
- My role
- Product Designer (Intern). I designed it and shipped the front-end code myself.
- What I did
- Redesigned the landing page (with a teammate), built a guided onboarding flow and a self-retiring activation checklist, and unified the nav across 5 pages.
- Result
- Four features shipped to the live product. The nav alone merged through 121 diverged commits without blocking three other in-flight features.
- ROLE
- Product Designer (Intern)
- TEAM
- Learvo. Landing page with one teammate; shipped into the live codebase.
- SCOPE
- Landing page, onboarding activation, navigation system, quiz review UX
At a glance
Highlights
4
features designed and shipped
5
core pages unified under one nav system
Replaced a cold, empty first session with a guided flow tied to real backend generation state
Designed an activation nudge that decays on its own instead of nagging long-term users forever
Shipped one consistent nav system across 5 pages while merging through 121 diverged commits
Redesigned the landing page with a teammate, then used live funnel data to see where visitors decide
Cut a fake "streak" feature rather than ship engagement numbers with nothing real behind them
What I Shipped
Shipped 01
Landing Page Redesign
ProblemThe old page looked like any startup site, and most visitors never scrolled past the fold. It also never answered the one question a skeptical student has: why not just ask a chatbot?
The Call
Show the product instead of describing it. With one teammate, I put a clickable demo in the hero, then answered the chatbot question straight away: "Learvo isn't a chatbot. That's the point."
- Try it, don't read about it: The hero is a live demo with tabs for quizzes, flashcards, summaries and mnemonics.
- Trust before features: Social proof, the chatbot comparison and the FAQ come before the feature grid.
- One button, one outcome: "Quiz me on my notes" in the nav, hero, FAQ and close.


First 10 days of data
Oct 27 to Nov 6, bots excluded.
232
real visitors
64%
clicked a button
17%
started onboarding
72%
click rate on phones, vs 56% on desktop
- People decide early. Only 15% reach the feature grid; 83% of first clicks come at or before social proof.
- The hero button wins. 81 people clicked it, the most of any button.
- People try to tap the demo. 29 phone visitors tapped the selected Quizzes tab 75 times, expecting it to respond.
Tracking began with this version, so there is no before-and-after yet.
ImpactA page that gets a busy, skeptical student to the point fast, then measured to see if it did.
View the live landing pageAI in the landing page
Where AI sped me up, and where the call stayed mine.
- Claude Code
- Claude Design
- Used it for
Claude Code: researched how learning and content algorithms work for Gen Z students and pulled out insights that shaped the product direction. Claude Design: built rough draft prototypes live in front of the team and changed them in real time during feedback sessions, so the team reacted to real screens instead of describing ideas.
- Where it fell short
Claude Design didn't deliver Gen Z designs that were up to par. It missed that the page should be short for students who value quality and efficiency, especially on mobile, and it didn't keep up with today's UI trends.
- What I changed, and why
Brought back the tabbed hero, with added text context and sub-feature previews for each feature, so the product showcase isn't overpowering because it is split up. Shortened the hero copy so the showcase moves to the top, for learning more at a glance.


What it made possible
We explored at least ten versions, and this one got the feedback that it was the best version the team has seen so far. It felt more modern without changing the design system or branding. Just launched, and I'm excited to see how the experiments go.
Shipped 02
Onboarding Checklist
ProblemUsers needed a persistent nudge to complete 4 core actions (upload, quiz, flashcards, summary), not just a one-time push at signup.
The Call
A checklist that never goes away is a nag, not a nudge. I built in decay on purpose: visible for a user's first 4 visits, gone for good on visit 5. Growth wanted persistence; I traded some completion pressure for not annoying users who'd already moved on.
- Two dismiss states, not one: The X dismisses for the current session and returns next time. It's only gone for good after visit 5, so an accidental close doesn't cost the nudge entirely.
- Cross-page completion tracking: Progress persists across pages via a shared store, instead of resetting per page.
- Collapsed variant for tablet: A waving-hand icon with a notification badge keeps the nudge alive on smaller viewports without eating layout space.



ImpactAn activation nudge built to lose the argument with itself over time, driving early engagement without becoming permanent nagware.
Shipped 04
Onboarding Quiz Flow
ProblemNew users landed cold on an empty dashboard after signup. Referral tracking also broke mid-flight because signup redirected before it could settle.
The Call
The easy fix was a fake progress bar counting to 100%. I designed against that: the generation screen shows the real backend phase, and if nothing moves for 25 seconds, it says so instead of leaving the user guessing.
- Guided first session: Upload, goal selection, customization, then generation, replacing the bare dashboard new users used to land on.
- Failure handling that doesn't dead-end: Generation failures surface a "Try again" button and auto-redirect instead of an error banner with no way forward.
- Fixed the state underneath the UI: Gated the quiz behind actual fresh signup (was firing on stale sessions), routed OAuth signups into onboarding, and scoped state per-user so it can't leak on a shared browser.






ImpactTurned a cold, empty dashboard into a guided activation flow that tells the truth about the backend.
Brand Identity
Problem: Learvo's green and blue palette already existed, but wasn't showing up consistently where it mattered most: the landing page and onboarding felt disconnected from the rest of the product.
The Call
Rather than introduce a new palette, I reinforced the existing one at the highest-visibility touchpoints and designed a mascot and doodle system to carry that identity through, instead of treating brand as a logo-only concern.

Lenny, the Study Buddy
Lenny is a sprout, tying the mascot directly to the learning theme of ever-growing progress. The personality is motivational but calm, deliberately not the high-pressure energy of a Duolingo-style mascot, showing up at the exact moments new users are most likely to bounce.

Early Sketches
Lenny went through several rounds of exploration: proportions, expression, and how much personality the glasses and posture should carry, before landing on the final sprout design used across the product today.

Doodle System
A playful, hand-drawn doodle style used across the same first-impression touchpoints as Lenny, plus preset doodle avatars for profile customization, extending that warmth into a functional UI element.
Impact: A consistent visual identity at the exact moments a new user forms their first impression, turning an already-correct palette into one that's actually recognizable.
How it unfolded
Timeline
Oct 2025
Lenny, the Mascot
Designed Lenny, Learvo's mascot, starting with sketches and landing on the final character design used across the product.
Dec 2025, ongoing
Doodle System
Started designing Learvo's hand-drawn doodle system, extended over time into preset profile avatars and more illustration touchpoints.
June 2026
Landing Page Redesign
Redesigned the marketing landing page to reinforce Learvo's brand identity at the first touchpoint a new user sees.
July 2026
Onboarding Checklist
Designed a persistent, decaying activation nudge for the 4 core actions, built to fade out for users who've already activated.
Sep 2026
Onboarding Quiz Flow
Shipped the guided upload, goal, customize, generate flow, replacing the empty first-session dashboard.
Nov 2026
Landing Page, Round Two
With a teammate, rebuilt the landing page around feedback and funnel data.
What I'd Do Next
- Make the hero demo answer a tap: Phone visitors already tap it. It should answer.
- Shorten the middle of the landing page: Only 15% reach the feature grid. Test a shorter page.
- Instrument the onboarding funnel: Add step-level analytics to the guided quiz flow to replace the current qualitative impact story with real drop-off and completion numbers.
- Validate the checklist decay window: Test the visit-5 cutoff against a longer or engagement-based threshold to confirm it's not hiding the nudge too early for slower-activating users.
- Build the streak feature properly: Stand up real activity-tracking infrastructure so the "weekly streak" concept cut from the quiz card banner can come back as something honest, not decorative.
Keep Wandering

Good Friends Poke
A course concept redesigning the fast-casual dining experience to reduce customer friction and peak-hour staff burnout.


