Qur’an for All

Problem

20,000 lectures behind look-alike tiles.

Every daily feature was hidden in a three-dot menu, and the player, the screen people used most, was the lowest rated in the audit at 2.1/5.

The challenge was to fix this without breaking the habits 200,000 people had already built.

Research

What people said, and what they actually did.

A bilingual survey ran through the WhatsApp groups and channels where users already were, plus moderated sessions on their own devices, with every task measured against targets agreed in advance.

The survey is self-report and six sessions are directional, so every session finding is either backed up at scale or flagged as unproven.

• ~1,900 survey responses
• 6 moderated sessions
• 3 weeks collection window

Findings

Users didn’t need new features. They needed the existing ones to work better.

Three intents kept surfacing across the survey and the sessions.

• Find. They know what they want. 55% never used Search, because it was hidden.
• Return. They’re mid-series. 60% had saved something they later couldn’t find.
• Explore. No particular goal. The smallest group, and stakeholders chose to prioritise current users.

Solution · Navigation

First, the app needed navigation.

A four-tab bar replaced the kebab, each tab mapped to one behaviour: Home is your activity, Browse is discovery, Library is structured content, Search is direct retrieval.

Home became a dashboard: Recently Played, Favorite Audios, Favorite Series and Downloaded.

Solution · Hardest call

Deciding not to redesign the Library.

Around 200,000 people had already memorised it, so it kept its shape. We only removed the categories the survey showed nobody used, going from 19 to 12.

One taxonomy rule then applied across 20,000+ files: one row per series, variants one level deeper, bilingual titles.

Solution · Player

Playback, rebuilt as two surfaces.

A persistent mini player for the background, and a full-screen player with a real scrub bar and exposed speed control for everything else.

Visible state went on every row: saved, downloaded, or already played.

Results

Shipped, then re-tested on the same tasks.

Eight weeks after release, using the same protocol, against targets set before testing. These come from moderated sessions rather than usage tracking, and Browse and onboarding remain unproven.

• 0% → 92% save-for-later completion
• 0% → 88% “is this saved?” first click
• 4.0 → 0.3 seek errors
• 2.1 → 4.5 player ease, out of 5

Learnings

Good judgment sometimes means doing less design.

The next cycle has two goals: analytics in the product, and closing the accessibility gaps that didn’t make the first release.

• The hardest call was holding back. Letting Browse and Library coexist was harder than designing either one.
• Showing state mattered more than adding actions. The tasks that improved most were the ones where the fix was making things visible.