K12 Education Mobile Product Design 2025
K12
Learning App
Intuitive Engaging Empowering
A thoughtful mobile learning experience designed for K–12 students — from lesson discovery to achievement tracking.
K12 Education Mobile Product Design 2025
Intuitive Engaging Empowering
A thoughtful mobile learning experience designed for K–12 students — from lesson discovery to achievement tracking.
The platform had content. It had students. What it didn't have was retention. I was brought in to redesign the mobile experience from the ground up — from how students first register, to how they find a lesson, track a study session and feel rewarded for coming back.
I owned the entire design process solo: research inputs, information architecture, component design, high-fidelity screens and handoff documentation. The result is a complete mobile product system built for daily use, not just a walkthrough demo.
Click any screen to view full size.
Before touching a frame, I mapped where the existing experience was breaking down. Platform audit, competitor benchmarking and user journey mapping gave me a clear picture of what students actually needed — versus what the platform assumed they needed.
Walked every screen of the existing app to surface friction. Navigation depth, lesson discoverability and progress visibility were the three areas with the most consistent drop-off.
Benchmarked Duolingo, Khan Academy and habit-forming apps to understand how progress framing, session rewards and timetable design drive return visits.
Mapped the end-to-end student journey — registration, subject selection, timetable use, study session and achievement review — to identify the moments where motivation stalled.
The institution had content. They had a platform. What they didn't have was students who wanted to come back. Low completion rates, passive browsing, and a navigation system that confused more than it guided.
Students opened the app but abandoned sessions early. No moment said "keep going to you're making progress."
Content was a flat list with no sense of journey. Students couldn't see how far they'd come or what to reach for next.
A single content path forced every student through the same flow regardless of subject strength or pace.
Dense screens and unclear navigation made the app feel like a chore before a single lesson began.
The product was organised around the actions students repeat most often: checking the dashboard, reviewing subjects, following a timetable, studying and tracking achievement. This reduced hidden navigation and gave the app a clearer daily-use rhythm.
The central insight was simple: students weren't disengaged because the content was bad — they were disengaged because the product never told them they were making progress. The UX direction was built around surfacing that signal early and often. Every screen had one job: show the student where they are and make the next step obvious.
"Make progress visible early, so students understand what to do next and why it matters."
Navy signals structure and authority — right for a platform schools and parents need to trust. Amber marks every reward moment and CTA, creating warmth without undermining the credibility of the overall system. Each subject gets its own hue, so the timetable is readable at a glance without needing labels.
Good UX is mostly what you choose not to do. Here's where I pushed back on the obvious solution and why.
A K12 audience spans a wide range of reading ability, attention spans and device contexts. The visual system had to carry meaning without relying on colour alone — and primary actions had to be reachable without hunting.
Large, high-contrast headings and generous card padding reduce cognitive load. Students can orient quickly without reading every label on the screen.
Subject colours are always paired with a text label — the experience never breaks for students with colour vision differences or low-contrast environments.
All primary actions sit in the bottom third of the screen, within natural thumb reach. No critical interaction requires precision tapping or nested menu navigation.
A design is only as good as what gets built. I structured the handoff so developers had everything they needed to build accurately without chasing clarification — component logic, screen states, spacing rules and interaction intent, all annotated and ready.
Cards, navigation bars, progress indicators and subject modules were designed as reusable patterns — not one-off screens. Each component had a clear usage rule to prevent ad-hoc decisions during build.
Onboarding, active study, progress review and achievement unlock were designed as a connected sequence, not isolated screens. Developers could see the full flow and understand context switches.
Spacing values, colour tokens, and interaction intent were documented against each screen. I stayed available through the QA phase to catch deviations before they shipped.
Shipping is the start of a design, not the end. With more time and real usage data, three things would move to the top of the backlog.
I'd want to watch students navigate from login to their first completed lesson. My hypothesis is that the study timer creates a moment of doubt — "am I doing this right?" — that a small onboarding nudge could eliminate.
The student experience is only half the product. Teachers who can see where students stall and intervene early are a significant retention lever — and that view doesn't exist yet.
Colour contrast holds for the main palette, but the muted subject label states need a formal check. Before any broader rollout, I'd run a full assistive technology pass — screen readers, dynamic text sizing and reduced motion.
The redesign gave students a direct line from login to their next lesson — no buried navigation, no guessing what to do next. Navigation was restructured from 11 states to 5. The component system was built to scale: every screen uses the same tokens, patterns and spacing rules so future features slot in without rework.