Overview
Building a learning platform from the ground up
Azvasa is a concept-based Learning Management System designed for schools — built to replace passive content delivery with interactive, motivated learning. The platform serves three distinct user groups: students engaging with quizzes and coursework, teachers managing classes and tracking performance, and school administrators overseeing the institution at scale.
This was a zero-to-production project. I came in with no prior LMS experience and had to learn the domain deeply before designing a single screen — understanding how curriculum is structured, how assessment works across grade levels, and what motivates students to actually complete work. The result is a product that went from mobile-first concept to fully delivered desktop web application.
Research
Understanding three very different users
Before any wireframe, I ran structured research across all three user groups — 15 students across different grade levels, 10 teachers across subjects, and school admin stakeholders. The goal was to understand how each group experiences learning, assessment, and school management — and where the pain was worst.
- Want to know exactly where they stand
- Motivated by streaks, scores, and visible progress
- Disengage when content is passive or repetitive
- Need quiz patterns that feel like a challenge, not a test
- Need to release quizzes and chapters by schedule
- Want to compare section performance at a glance
- Frustrated by manual attendance and progress tracking
- Need to see who is struggling before it's too late
- Needs institution-wide visibility, not per-class detail
- Wants to monitor teacher training completion
- Manages syllabus, academic calendar, and policies
- Requires audit-ready reports on engagement and scores
"Students don't disengage because the content is hard — they disengage because they can't see any progress. The motivation layer isn't a nice-to-have; it's load-bearing."
Research Insight — Azvasa
Design Process
From personas to production-ready system
After synthesising personas, I built a full information architecture covering all three roles — mapping how content flows from admin to teacher to student, and how assessment data flows back up. Then I designed mobile-first, treating the phone screen as the constraint that forced every interaction to be deliberate and the most important content to surface first. The desktop web application was designed as an expansion of that model, not a separate product.
Product Screens
Interactive quizzes, teacher dashboards, and the login experience
The three screens below represent the breadth of the design system — from the student quiz experience with drag-and-drop interaction patterns, to the teacher's performance dashboard with section-level analytics, to the branded login page that sets the platform's visual tone.
Design Decisions
The interactions that made the difference
Concept-based quiz types
Beyond standard MCQs, I designed interactive question types including drag-and-drop match-the-following, fill-in-the-blank, and image-based questions. The goal was to test understanding, not recall — forcing students to actively construct answers rather than recognise them.
Motivation layer
Research showed students disengage without visible progress signals. I built streak tracking, animated score reveals, grade badges, and leaderboard positions directly into the student experience — not as add-ons, but as structural elements of every session.
Question navigation dots
The quiz interface includes a persistent question-map at the bottom — colour-coded attempted vs unattempted dots — so students always know where they are in the assessment and can jump to any question without losing context.
Teacher analytics at a glance
The teacher dashboard shows chapters-vs-completed, quizzes-released-vs-taken, and training-vs-completion in a single view. Section comparison charts let teachers immediately spot which class needs attention — without drilling into individual records.
Interactive Prototype
Explore the Azvasa Figma prototype
The full mobile app prototype is embedded below. Navigate through the student quiz flow, onboarding screens, and the teacher dashboard to experience the interaction model first-hand.
Outcomes
What Azvasa delivered
Reflection
What I took from this project
Azvasa was my first full LMS build and one of the most demanding projects I've worked on — not because of the design complexity, but because of how much domain knowledge I had to build before I could design responsibly. I had to understand curriculum structure, assessment theory, grade logic, and institutional hierarchy before a single wireframe made sense.
The mobile-first constraint was the best thing that happened to the product. It forced prioritisation at every step. Every element on the phone screen had to earn its place, which made the desktop expansion far more focused and less cluttered than if we'd started there.
The biggest lesson: motivation design isn't cosmetic. Streaks, scores, and animations aren't decoration — they're the mechanism by which students decide whether to come back tomorrow. Getting that layer right was as important as any information architecture decision.