i‑Learn Platform.
My role.
Product & UX/UI designer for the student and guardian experience and the operations console.
- Onboarding, placement and teacher matching
- The syllabus and lesson experience
- The guardian control center, wallet and family sub-accounts
- The admin console the Nawah team runs the programs from
- The teacher assessment flow
- Free to families — funded as a waqf, so the product carries the operational load
- Two audiences on one data spine
- Programs authored by the team without a release
- Qur'an and Arabic teaching, with recitation goals tracked separately
The brief.
Nawah runs Qur'an and Arabic teaching programs — the kind of operation that usually lives in a stack of spreadsheets, a wall of WhatsApp threads, and a shoebox of paper receipts. Matching a student to the right teacher, keeping a schedule, tracking who finished which level, handling a missed session — every one of those was a manual job.
They wanted a single platform to run the whole thing, and a model where families pay nothing: the program is funded as a waqf (endowment), so the product had to carry the operational load that fees normally pay people to do.
The idea.
Two products sharing one spine. The student side behaves like a course app: sign up, take a short placement test or pick a ready plan, get matched to a teacher and a weekly schedule, then land in an interactive syllabus. The admin side is the console the Nawah team lives in — enrolments, teachers, sessions, and the finance ledger behind the free-to-families promise.
Teachers come in through their own gate: an "Am I a tutor?" assessment — multiple choice plus a short live recitation recording — screens applicants before they ever reach a student.
Matched, not just enrolled.
Signup ends with a person, not a payment screen. The student picks a program, and the platform either surfaces an available teacher whose slots fit or builds a weekly plan around the times they gave — so the first thing they see after joining is a real schedule with a real name on it.
A live map of the course.
Each program opens onto units and lessons on a single scrollable path — locked, open, or done — with a progress score, a points total, and a "resume learning" button that always points at the exact next thing. Nobody has to ask a teacher "where was I?".
Read it, watch it, then prove it.
A lesson holds mixed resources — video, documents, links, an in-page reader — and closes with a quiz that has to be answered correctly to move on, with right/wrong states written to encourage another try rather than end the attempt. Qur'an sessions track recitation goals separately, with a "request re-evaluation" path baked in.
One account, a whole family.
A guardian runs a main account with a sub-account per child — each with its own programs, schedule and progress. The wallet handles invoices, refunds, referral credit, gifts and late-session compensation, and a single screen requests a vacation, a pause, or an account transfer without an email to support.
Key decisions.
-
End onboarding on a person, not a payment screen
Why Matching a student to a named teacher and a real weekly schedule inside signup means there is nothing to come back and set up later.
-
Turn every dead end into a form
Why Vacations, pauses, re-evaluations, refunds and account transfers each got a screen, which kept a fee-free operation from drowning in support requests.
-
Treat the admin console as a first-class product
Why The free-to-families model only works if the team can run enrolments, teachers, sessions and finance from one place.
Trade-off Roughly half the design effort went to a surface families never see.
-
Require a correct quiz answer to move on
Why It keeps progress honest; right and wrong states are written to encourage another try rather than end the attempt.
The ship.
i-Learn shipped as a web platform for students and guardians, a companion native app for the student's day-to-day (quick entry, notifications, wallet), and an operations console for the Nawah team — enrolments, teacher accounts, sessions, messaging and the finance ledger in one place.
The interactive curriculum is content-driven: materials, programs, levels, units, lessons and quiz banks are all authored in the admin, so the team can stand up a new program without a release.
What shipped.
Enrolments, schedules, teacher matching and payments that ran on spreadsheets, WhatsApp threads and paper receipts now run in one platform — and the team can stand up a new program without a release.
What I'd do again.
End onboarding on a person. Matching the student to a named teacher and a real schedule inside signup left nothing to "come back and set up later".
Design the operations console as a first-class product. The free-to-families model only works if the team can run everything from one place; the admin got the same rigor as the student app, not a table dump.
Give every dead-end a form. Vacations, pauses, re-evaluations, refunds, account transfers — every "you'll have to contact us" became a screen, which is what kept a fee-free operation from drowning in support.