i‑Learn Platform.

ClientNawah
RoleProduct & UX/UI Designer
TeamDesign + product & curriculum team
Timeline2021
PlatformWeb platform + native student app
i-Learn landing page — 'With you every step of the way'

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.

"One place for the student, one console for the team — and no invoice ever lands on a parent."

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.

Signup — choose a plan type for the program
Signup — let the system build a weekly schedule around the student
Step 01 · Onboarding

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.

Step 02 · The syllabus

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?".

Step 03 · Inside a lesson

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.

Step 04 · Control center

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.

Signup — an available teacher matched to the student's chosen times
Interactive syllabus — units and lessons on one path with a progress score
Inside a lesson — a quiz question with encouraging right/wrong states
Student control center — programs, schedule and progress per sub-account

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.

Inside a lesson — mixed resources: video, documents and links

What shipped.

0
Fees to families
Funded as a waqf — the wallet, ledger and compensation logic all sit inside the product, not on a parent's bill.
2
Sides, one spine
A course-app experience for students and guardians, and an operations console for the team, on the same data.
1:1
Student to teacher
Placement, a vetted teacher and a weekly schedule handed over in a single signup — no back-and-forth to get started.
Test Yourself — a placement question with multiple choice
Control center — a guardian's list of child sub-accounts

What I'd do again.

End onboarding on a person. Matching the student to a named teacher and a real schedule inside signup did more for retention than any welcome screen could — there's 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.

Next case
Reportage