A clickable prototype of the redesigned QuranFlow app — the semester program, rebuilt around one question: where am I, and what's next?
Best on a phone — everything is tappable.
The app with a rail underneath, walked one screen at a time.
Pick the journey you are reviewing.
You are Sarah, on your first day.
You are Sarah, in Week 8 of 15.
You are Hana, back after Level 4.
You are Amina, with the coach's hat on.
Reviewing all of it? The complete tour runs every journey in sequence — 60 chapters, end to end.
The same build with the rail and the notes stripped out — just the app, in first person.
Pick the journey you want on your phone.
Sarah, nothing set up yet.
Sarah, Week 8, four tabs live.
Hana, a year in.
Amina, coach's hat on.
Want every screen at once? The whole app opens with no journey selected — all four, free to explore.
Every journey laid out side by side — new students, Year 1's submission loop, Year 2's appointment loop, the coach's role-gated lane — showing where they diverge, where they share a screen, and which questions are still open. Corrected against the Jul 27 review with Lejla: sixteen tracked questions, nine now carrying her answers.
Open →What the app says while it is closed: the lock screen, the widgets, the Dynamic Island. Status-gated the same way — Year 1's week, Year 2's next appointment by plan, and two quiet doors for the student still waiting on placement. Never a deadline.
Open →Four entrances, one prototype. An entrance is a starting point, not a different build. Each one drops you into a single journey — new students, Year 1, Year 2, or the coach — with only that journey's chapters on the rail. The complete tour is 60 chapters in seven acts; an entrance is a slice of it, so you review the journey you know without walking someone else's.
The rail tells you where you are. Under the phone, every chapter shows its act and its screen code — YEAR TWO · S37 — with a note on what you are looking at and why. Step with the ‹ › buttons, or the arrow keys on a laptop. Tap the chapter title to see the whole list for that entrance.
Codes are global and stable. S14 is the same screen in every entrance, in the app, and on the flow map. Student screens carry an S, coach screens a C. Giving feedback? Say the code in a voice note — "on S37, the date is doing too much" — and everyone finds the screen you mean.
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.
Students were doing the work — watching, reciting, showing up — and still felt lost in their own program.
"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.
The live schedule sat five clicks deep behind an external calendar link. Students missed sessions they fully intended to attend.
Coach feedback arrived and students never saw it — the "Feedback" button read as give feedback, and notifications carried no context.
A hi-fi prototype of the iOS app. Clickable, not final art. It shows structure and direction.
Two members, four entrances. Sarah arrives new — she signs in with the account she made when she enrolled on the web, records a first recitation, and sits at Level 0 until the team places her — 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. Amina works in the same app with the coach's hat on: 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.
Progress is a real semester, not a fragile counter. Nothing shames, nothing expires at midnight for effect.
Every screen shows what's next, one week reference, one primary action. Depth on demand, never all at once.
Every session renders in the viewer's timezone, stated once per screen — never a guess, never someone else's clock.
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.
Suggested path for a first read: pick an entrance and tap through the tour, 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.