The Hifz classroom does not look or sound like any modern computer lab. The Ustad sits cross-legged on a low wooden platform or cushioned carpet at the front of the hall. Around him, fifteen to twenty-five young boys sit with wooden rehal bookstands, rocking gently back and forth as they recite the Holy Quran in soft, overlapping cadences.
One by one, each student steps forward, kneels beside the Ustad, and recites from memory. The Ustad listens with acute, razor-sharp focus. Every single vowel lengthening, nasal sound (ghunnah), and letter articulation point (makhraj) is scrutinized. If the student falters, the Ustad corrects him instantly. And when the recitation ends, the Ustad has to record how the boy performed.
When I sat down with Sheikh Abu Bakr—an esteemed Hifz teacher with thirty-two years of teaching experience across three districts—he pulled out his personal notebook. The pages were yellowed, hand-ruled with blue ink, and filled with miniature Arabic and Bengali notations. It was a masterwork of dedication. But as he admitted with a sigh: "Over thirty years, I have lost this book three times during relocations and monsoon floods. When the book is gone, the boy's history is gone."
The Real Challenge: Designing for Non-Tech Specialists
Building an app for startup developers or corporate managers is easy: they understand modal dialogs, search filters, hamburger menus, and dropdowns. But our primary user here is an Ustad who may be sixty years old, possesses an unbroken chain of Quranic transmission (Ijazah), carries immense respect in his community, but owns a budget Android phone that he uses almost exclusively for voice calls and voice messages.
He is not interested in technology for technology's sake. If our interface requires him to pinch-to-zoom, type names on a tiny on-screen keyboard, or navigate four nested screens during class, he will rightfully set the tablet aside and go back to his notebook.
We set ourselves an aggressive design target: an Ustad must be able to log an entire classroom of 18 students—including lesson quality, ayah ranges, and specific error types—in under 45 minutes, with zero typing.
The Four Design Decisions That Made It Work
1. Tablets, Not Mobile Phones
Our initial prototype ran on standard mobile phones. It failed within fifteen minutes of classroom testing. The screen was too cramped, the Ustad had to hold the device with both hands, and small fonts strained older eyes. We pivoted to inexpensive 10-inch Android tablets mounted on low desktop stands next to the Ustad's seat. The tablet looks and behaves like a digital rehal: it stays in place, uses large readable fonts, and can be operated with a single hand while the Ustad maintains eye contact with the reciting student.
2. Zero Keyboard Input During Active Sessions
Every single interaction during a live recitation is purely tap-driven:
- The teacher sees a grid of student portrait cards with clear Bengali names and current Juz numbers.
- Tapping a student opens the quick-entry sheet for today's session: সবক (Sabak), সবকি (Sabki), or মঞ্জিল (Manzil).
- Recitation performance is captured with large, color-coded status pills: চমৎকার (Excellent), উত্তম (Good), চলতি (Acceptable), and দুর্বল (Needs Revision).
- Ayah boundaries are adjusted with rapid
+/-stepper buttons rather than numeric text fields.
3. Classical Error Types Mapped to Touch Targets
Hifz errors are not vague mistakes; classical Quranic pedagogy categorizes recitation faults into precise disciplines. We built six dedicated error buttons directly into the tablet interface:
| Error Category | Bengali UI Label | Pedagogical Impact |
|---|---|---|
| Tajweed (তাজবীদ) | তাজবীদ ত্রুটি | Madd length, Ghunnah timing, Qalqalah application rules |
| Makharij (মাখরাজ) | মাখরাজ অশুদ্ধ | Letter articulation points (e.g., confusing ض with ظ or ق with ক) |
| Wasl (ওয়াসল) | ওয়াসল / সংযোগ | Incorrectly joining verses or neglecting silent hamzat al-wasl |
| Waqf (ওয়াকফ) | ওয়াকফ / বিরতি | Stopping at forbidden junctures or breathing incorrectly |
| Repetition (তাকরার) | পুনরাবৃত্তি | Stuttering or repeating lines due to memory hesitation |
| Omission (নকস) | শব্দ বাদ পড়া | Skipping words or complete ayahs unnoticed |
When an error occurs, the Ustad taps the corresponding error pill and selects the ayah number. That is all. The system tags the exact surah, ayah, date, and error classification into the database in the background.
4. The 30% Button Size Rule
During our very first classroom test, we noticed Ustads occasionally double-tapping adjacent buttons by mistake. Their fingers are accustomed to turning physical paper pages, not capacitive touch screens. We immediately redesigned the CSS tokens: minimum touch targets were increased from 44px to 62px, padding was widened, and haptic vibration feedback was enabled for every logged entry.
The Verdict from the Field
At the end of a two-week pilot in a madrasa in Gazipur, I asked Sheikh Abu Bakr how he felt about the system. He looked at the tablet screen where today's session summary was displayed—18 boys logged, error summaries categorized, parent notifications already dispatched via SMS.
He turned to me and said in Bengali: "আগে খাতায় লিখতাম, পরে ভুলে যেতাম। এখন আঙুল ছুঁইয়ে দিই, যন্ত্র মনে রাখে।" ("Before, I used to write in a book and forget later. Now I touch with my finger, and the machine remembers for me.")
That single sentence proved we were on the right track.
Mustafa Kamal Hossain
Founder & Principal Engineer at Manfi. Passionate about Laravel, SaaS architecture, and high-performance engineering.