Q
QuranFlow · AlMaghrib Institute · Product Direction

Fifteen weeks,
one rhythm.

A clickable prototype of the redesigned QuranFlow app — the semester program, rebuilt around one question: where am I, and what's next?

TAKE THE GUIDED TOUR →
Reviewing one side? The same tour, split in two for sharing:
The student app The coach app

Best on a phone — everything is tappable. Opening the app? Tap Share → Add to Home Screen for the full-screen experience.

Why we redesigned

Students were doing the work — watching, reciting, showing up — and still felt lost in their own program.

01

Disorientation

"8 out of 15" never read as Week 8. Students didn't know what week they were on, when the semester started, or what to do today.

02

Missed sessions

The live schedule sat five clicks deep behind an external calendar link. Students missed sessions they fully intended to attend.

03

Unnoticed feedback

Coach feedback arrived and students never saw it — the "Feedback" button read as give feedback, and notifications carried no context.

The shift

Today's app

  • A collection of features — videos here, schedule there, feedback somewhere
  • Schedule five clicks deep, in someone else's timezone
  • Progress as "8 out of 15", meaning unclear
  • Feedback that arrives silently

The redesign

  • The Weekly Rhythm — every screen answers "Week 8 of 15" and shows only what's next
  • Sessions one tap away, always in your own timezone
  • One loop per week: Watch → Record → Feedback, with two attempts and a coach reply within 48 hours
  • Feedback that announces itself — "Feedback ready", in gold, on the words you recited
What you are looking at

A hi-fi prototype of the iOS app. Clickable, not final art. It shows structure and direction.

Two members, two journeys. Sarah arrives new — enrolls on the web, books a first assessment, is placed in Level II — then lives Week 8 of her 15-week semester: the week's tajweed lesson, recording Al-Mulk 67:1, her coach's notes on the exact words. Hana returns for Year 2, where appointments replace submissions.

The coach's side is included. The last chapters cross to the coach section: the review queue, reviewing a recitation, and turning a 20-minute one-to-one into sent notes in minutes.

Real curriculum, demo data. Lessons and verses are drawn from the actual program; names, dates, and counts are fixtures.

How to move through it

It opens into a guided tour. A rail under the phone walks 57 chapters in order, in seven acts: arriving → getting oriented → the weekly rhythm → year two → sessions & coaching → learn & progress → the coach side. Step with the ‹ › buttons, or the arrow keys on a laptop.

Jump between journeys. Tap the chapter title on the rail to open the act list — straight to Year two or The coach side — or tap the strip beneath it. Each act is one journey from the flow map.

Looking for a level? The levels live inside the student journey as acts: placement and the Level 0 wait are Arriving (S01–S09), the Year 1 weekly loop — the same shape for Levels 1–4 — is The weekly rhythm (S17–S28), and Year 2's appointment rhythm is Year two (S29–S37).

Giving feedback? Every chapter carries a screen code on the rail — S14 for student screens, C03 for coach screens. Say the code in a voice note and everyone finds the screen. The student app and the coach app are the same walkthrough split into two separate experiences, made to be shared on their own.

Or explore freely. Tap on the rail and just use the app — four tabs (Today · Learn · Sessions · You), the lesson, the recorder, booking. Everything is live.

Prefer no chrome at all? The App is the same build with the tour hidden — first-person, like the shipped product.

What we held onto

No streaks, no guilt

Progress is a real semester, not a fragile counter. Nothing shames, nothing expires at midnight for effect.

One thing at a time

Every screen shows what's next, one week reference, one primary action. Depth on demand, never all at once.

Times are always yours

Every session renders in the viewer's timezone, stated once per screen — never a guess, never someone else's clock.

It reaches the lock screen

Week, next session, and feedback meet the student before the app opens. Reading the week's verse there and never opening the app is a success.

Six ways in
Start here · Guided tour

The walkthrough

The app with a narrated rail — 57 chapters in seven acts explaining what you're looking at and why it's designed that way, with a screen code (S14, C03) on every chapter for feedback.

Open →
For sharing

The split tours

The same walkthrough in two self-contained pieces, each shareable on its own: students see the student journey (S01–S51), coaches and TAs see the coach side (C01–C06).

Student app →   Coach app →
Try it

The app

First-person, no walkthrough chrome. Starts at sign-in, lands in Week 8. Tap through like the real thing.

Open →
For reviewers

The reconciliation board

How two design explorations became one app: screen-by-screen comparison, every decision adjudicated and logged, closed with the final design review.

Open →
Outside the app

The ambient layer

The lock screen, widgets, and Dynamic Island — status-gated like the app: Year 1's week, Year 2's appointments by plan, and the arriving student's two quiet doors — never a deadline.

Open →
By user status

The flow map

Every journey through the app — new student, Year 1, Year 2, coach — where they diverge and converge, corrected against the Jul 27 review with Lejla. Sixteen tracked questions; nine now carry her answers.

Open →
The documents
Feedback Synthesisthe "why" — start here; all four stakeholder sources, ranked Product Specscreen-by-screen: states, actions, routing, role gating Design Systemtokens, type scale, components, accessibility Data Modelentities, state machines, business rules, integrations Traceabilityevery ask → designed / deferred / rejected, with evidence Implementation Plantech recommendation + dated delivery plan for the September launch Design Rules & Auditthe 8 binding rules + per-screen audit log Overlap Reviewconflicts between sources, adjudicated — this wins ties Widget Explorationthe full reasoning behind the ambient layer Decision Logevery decision taken building the walkthrough

Suggested path for a first read: tap through the walkthrough, skim Feedback Synthesis for the why, then go where your role takes you — Product Spec and Data Model for engineers, Traceability for the PM, the reconciliation board for design reviewers.