←Back to case studies
BrightChamps · Learner App

Project
Parent app for iOS, Android and tablet: home, classes, curriculum, tasks and profile
Industry
EdTech · live 1:1 classes for ages 6–16 in 30+ countries
Services
UX researchInformation architectureInteraction designUI designEdge-case design
Role
Sr. UI/UX Designer · with 1 PM, 1 tech lead and QA · 9 weeks · shipped 25 Sept 2023
Cover from Figma
  1. 1
    Is that my time?City and time zone sit on top.
  2. 2
    Which child?Switch on the name.
  3. 3
    Did the last one happen?Completed is one tab away.
  4. 4
    When's the next class?Date and time, first thing.
  5. 5
    Can I move it?Reschedule on the card.
  6. 6
    Is it working?Progress and certificates in Profile.

Story

BrightChamps teaches coding, financial literacy, robotics and maths to children in live one-on-one classes. The Learner App is where a family manages all of it.

Between June and August 2023 it was quietly losing them. Monthly users fell from 23k to 17k. Time in the app dropped from nearly ten minutes to under six. Nothing had broken. People had simply stopped finding a reason to open it.

One line in the product brief reframed the work:

“Most of the users on the app are parents, not kids.”

It was called the Learner App and designed like a classroom. The people holding the phone were parents, checking in between other things. They didn't come to learn. They came to verify.

Impact

Every metric had a target and a date before release. Thirty days after launch, all three were back.

Monthly active users

Launch · 25 Sept23kJune17kAugust23k25 OctMeasured monthly, 2023

Time in the app, per user a month

Launch · 25 Sept9m 40sJune5m 51sAugust9m 40s25 OctMinutes and seconds
14 → 0Negative Play Store reviewsJuly–August, then the 30 days after launch
100K+Downloads on Google PlayPlus the App Store, on phone and tablet

Challenges

The web dashboard held the full picture of a child's course. The app held a fragment. Every real task ended somewhere else.

01.ReschedulingRescheduling or cancelling meant the web dashboard or a phone call to support. A weekly slot has to survive school events, travel and sick days.
02.AttendanceAttendance, credits used and credits lost lived in the backend. A parent paying per class couldn't see what was left.
03.HomeworkQuizzes, assignments and assessments had no status a parent could read. No due date, no score, nothing pending.
04.ProgressConcepts covered, certificates and progress sat in three systems. None of them was the app.

Empathize

Where every parent task actually happened

We listed every action a parent takes across a course, then marked where each one really lived: the app, the web dashboard, email, or a call to support. Most were not in the app.

Parent taskBeforeAfter
Move a classWeb dashboard or a call to supportReschedule on the class card
Check the last class happenedBackend only. Nothing a parent could seeCompleted class with concepts learnt
See classes and credits leftBackend onlyCurriculum: paid, done, left, lost
See homework statusNo readable status anywhereMy Tasks: Pending, Submitted, Score, Missed
Know if it's workingSpread across three systemsProfile: courses, progress, certificates

About the research

  • The task audit above, across app, web, email and support.
  • Support call logs. The account holder was almost always the one calling.
  • Usage data from June to August: monthly users and time in the app.
  • Store reviews. Parents named the features they had lost.

Define

Four sources, six findings. Each one changed something on screen.

ParentsThe account holder, almost always a parent, was the one calling support. Not the child.Support logs
SchedulesMoving a class was the call that kept coming back. School events and travel break a weekly slot.Support logs
SiblingsFamilies registered two children on one number, and the app showed them as one child.Support logs
Time zonesFamilies enrol in one country and take classes from another. Every time has to be right where they are.Support logs
Lost featuresReviews named what the update took away: chat with the teacher, curriculum, cancelling.Store reviews
PaymentsA pending instalment can't hide what a family already paid for. Lock the future, not the past.Task audit

One insight tied them together, and four rules let the team apply it without me in the room.

AnswerAnswer, then actEvery screen opens with the fact a parent came for.
StatesDesign the block firstCancelled, locked, paused and missed decided the layout.
FamilyOne number, many kidsSwitching children sits on the home header.
CostFriction in proportionThree light steps to move. A typed word to cancel.
Single insightParents open the app to check, not to learn.Six questions. One home screen.

Personas

Two parents drove the structure. Two edge cases decided its limits.

C
The checking-in parentOne child · one course · opens the app 2–3 times a week
Is Tuesday still on, and did last week actually happen?

Goals

  • See the next class without hunting
  • Confirm the last class ran
  • Move a class when school gets in the way

Frustrations

  • Calls support to reschedule, twice a month
  • Can't tell a cancelled class from a missed one
T
The two-kid parentTwo children · one phone number · often two courses
I registered both kids on my number. I only see one of them.

Goals

  • Switch children without logging out
  • Keep two courses separate
  • Track two schedules

Frustrations

  • One account shown as one child
  • Support routed to the wrong team
Edge caseThe relocating familyEnrols in one country, takes classes from another. Every time has to be right where they are standing.What it gotA timezone control on the home header, with the city shown.
Edge caseThe account on holdAn instalment is pending. Locking the whole app would hide what they already paid for.What it gotUpcoming classes lock with a reason. History and certificates stay open.

Ideate

Six questions, five tabs

Anything that didn't answer one of the six questions lost its claim on the home screen. Pick a question to see where it's answered.

  1. HomeNext six classes, timezone, switch child
  2. CurriculumAttendance, history, what's next
  3. My TasksQuizzes, assignments, assessments
  4. ScheduleAdd a class or change the week
  5. ProfileCourses, certificates, support

User Flows

From “I need to move Tuesday” to done

The two flows parents used to call support for. Moving is frequent and forgiving. Cancelling costs a credit and can't be undone, so it asks for more.

Reschedule · three light steps

  1. Class card
    • Next class first
    • Reschedule on the card
  2. 01Reason
    • Asked by teacher
    • Out of station
    • Health
    • School activity
    • Personal work
    • Other
  3. 02Day and slot
    • Next 10 days
    • Teacher's open slots only
  4. Rescheduled
    • Message with both times
    • Teacher notified

Cancel · one deliberate step more

  1. Class card · More
    • One layer down
    • Not on the surface
  2. 01Reason
    • The same six reasons
    • So the data compares
  3. 02Confirm
    • Uses one class credit
    • Class, date and time
    • Type CANCEL to enable
  4. Cancelled
    • Receipt with class number
    • Credits update on Home
    • Teacher emailed
Rule · both flowsWithin 2 hours of the start, both actions turn offDisabled, not hidden, with the reason shown. A teacher's preparation is never wasted.

→Friction in proportion to cost: three light steps to move, a typed word to cancel.

Prototype

Try both flows on a working rebuild. Toggle the two-hour lock to see the rule.

T
Hello,Troy ▾
IST · Bengaluru
48Paid
35Done
12Left
1Lost
Upcoming classes
</>
Coding · Class 156 · Teacher JacobLoops in PythonTue, 15 Aug · 5:30 PM
</>
Coding · Class 157 · Teacher JacobLists and dictionariesFri, 18 Aug · 5:30 PM
₹
Financial Literacy · Class 34 · Teacher JacobNeeds vs wantsSat, 19 Aug · 11:00 AM
  1. 1
    Pick an actionReschedule on the card, or More → Cancel class.
  2. 2
    Say whyOne tap. The reason comes before the time.
  3. 3
    Pick a day and slotOnly the teacher's real slots, ten days out.

Experience Validation

The release was judged by what parents did in the 30 days after launch, and by what they wrote in the stores.

Monthly active users
17k23k
Minutes in the app, per user a month
5m 51s9m 40s
Negative Play Store reviews
140

Before launch30 days after

Before the redesign
“The classes are awesome but the updated app is horrible, lost so many useful features like chat with teacher, see curriculum, cancelling classes…”
Indu R.Google Play · Aug 2023
After
“Superb app. Took my child's learning to the next level”
Yatharth S.Google Play · May 2025
Still to do
“Need to simplify rescheduling, cancelling the class, adding the class.”
A parentGoogle Play · May 2024

Design Brought to Life

Fourteen screens, each shaped by one decision. Tap through them as you would the app.

Learner App, Home screen

01 of 14

Home

Six classes in the order they happen. Tomorrow is never below the fold.

Tap the screen as you would the app. Tap anywhere else to see what's tappable.

The messages that carry the rules

Nine shipped. Each had to survive being read in four seconds, at a school gate.

Cancelled by parent“Your coding class No. 155 has been cancelled.”A receipt. The fact and the class number.
Cancelled by teacher“…cancelled on teacher's request.”Stays until dismissed, and is mirrored by email.
Rescheduled“…rescheduled from Aug 15, 5:30pm to Aug 18, 5:30pm.”Both times, so the parent can check the change.
Class added“A coding class has been added on Aug 18, 5:30pm.”One class names the slot. Several just say so.
Instalment pending“Our counsellor will contact you soon for payment.”Locks upcoming classes and names a human.
Package complete“You've successfully completed all your classes.”An empty list reads as a milestone, with the upgrade route.

Takeaway

The app was designed like a classroom and used like a receipt. Rebuilding it around the questions parents actually open it for brought back the people it had been losing.

Numbers set before releaseEvery metric had a target and a date, 30 days after launch. The release was judged on what parents did, not how it looked.
Talk to parents, not just support logsWe knew who held the phone from who called support. Six interviews would have settled arguments that took weeks.
Scope to survive a moving baseThe dashboard was changing under us, so v1 left out onboarding and payments. Half an app that stays correct beat a whole one that breaks.
Measure support calls nextThe real test: does a parent who reschedules in the app ever call support to move a class again?

More work

Was this case study useful?

Was this case study useful?

There's more behind this one.

Want the full story?Ask me about it.

© 2026 Adnan Murad · Senior UI/UX Designer, Bengaluru

Create a free website with Framer, the website builder loved by startups, designers and agencies.