Selected Works EduSphere  ·  Case study
Mobile Learning Platform · 2021

EduSphere

Turning a sprawling course catalog into a path people can finish.

ResearchWireframingUI DesignPrototypingiOSAndroid
RoleUX/UI Designer
PlatformiOS & Android
Year2021
ToolsFigJam, Miro, Zeplin, Figma
EduSphere cover
Overview

EduSphere is a mobile learning platform designed to make knowledge accessible to everyone. Users explore categories, enroll in courses, and track their progress — with an intuitive interface and personalized recommendations that support continuous learning.

The challenge

Learners struggle to discover courses that match their goals, lack a structured path, and get lost in cluttered interfaces that make progress hard to track.

People don't leave because they lost interest — they leave because they lost their place.
Goals
1

Simplify course discovery with personalized recommendations

2

Improve engagement with structured course navigation

3

Offer transparent progress tracking for learners

4

Enhance accessibility with a modern, intuitive UI

Target audience
Primary

Young professionals (18–35) upskilling fast in tech, design, and business.

Secondary

Students and lifelong learners seeking affordable, structured online courses.

User research

Method Online survey · 50 respondents

68%
can't find the right course
72%
value progress tracking
50
survey respondents
  • 68% struggle to find courses matching their goals
  • 72% value progress tracking and clear milestones
  • 55% were frustrated by cluttered UI in competitors
  • Users prefer modular course design with clear chapters
Competitive analysis
CourseraUdemyEduSphere
Course discoveryLimited filtersWide varietyPersonalized recommendations
Progress trackingBasicBasicDetailed progress & milestones
Pricing flexibilitySubscription-basedPay per courseFlexible & affordable plans
User experienceFunctionalCrowdedClean & modern
Mobile-first designAverageAverageFully optimized
Pain points

Difficulty discovering the right courses

No structured learning path

Weak progress-tracking systems

Overloaded, confusing UI in other apps

User persona
Alex Carter
Alex Carter
Age25JobJunior UX DesignerLocationBerlin, Germany

Alex is a junior UX designer who wants to quickly improve his skills and stay current. He has tried different e-learning apps but often lost motivation to cluttered interfaces and unstructured courses. He values a clear roadmap and progress tracking.

Personality
  • Ambitious
  • Goal-oriented
  • Mobile-savvy
  • Prefers visual learning
Goals
  • Learn new skills efficiently to advance his career
  • Track learning progress with clarity and milestones
  • Access affordable, structured courses
Pain points
  • Gets lost without a structured content flow
  • Frustrated by cluttered, confusing interfaces
  • Struggles to stay motivated in long, unorganized courses
Motivations
  • Career growth and promotion
  • Building a standout skillset
  • Transitioning to a senior role within 2–3 years
Process
01

Discover

Stakeholder interviews, user research, and an audit of the current experience to understand the real problem.

02

Define

Synthesizing findings into clear problems, user goals, flows, and the information architecture.

03

Design

Wireframes to high-fidelity UI, built on a component system and refined through iteration.

04

Deliver

Prototyping, usability testing, and a documented hand-off engineering can build from confidently.

Key screens
EduSphere – Home
Screen 1

Home

A top area surfaces courses in progress for continuity. Below, Categories and Newly Added Courses spark interest and motivate further learning.

EduSphere – Discover
Screen 2

Discover

Trending categories and the user's chosen topic tags drive tailored, engaging course recommendations.

EduSphere – Course Detail
Screen 3

Course Detail

Duration, assignments, and downloadable content at a glance. A concise description and reviews build trust; a fixed bottom bar shows price and Add to Cart.

All screens

6 screens from the final design — tap any to enlarge.

Reflection

Usability testing before hand-off caught two flow-breaking assumptions that would have been expensive to fix in code.

Next project

Aidopolis