About the Project — Awliyah

Inspiration

Awliyah was inspired by a simple but deeply felt gap: while the Qur’an is recited by millions every day, access to qualified Huffaz for one-to-one listening and correction is uneven and often informal. Many people rely on local availability, personal networks, or irregular online calls.

At the same time, modern tools make global, real-time connection effortless—yet very few products treat Qur’an recitation with the adab, calm, and intentionality it deserves. Awliyah was born from the idea that technology should quietly serve sacred practices, not overwhelm them.

The vision was to create a space where:

Huffaz can offer their time intentionally
Learners can request sessions respectfully
The experience feels spiritual, focused, and human—not transactional

What I Learned

Building Awliyah reinforced several lessons:

UX matters more in sacred contexts
Minimalism, pacing, and restraint are features—not omissions.
Real-time systems are as much about trust as technology
A global map doesn’t just show availability—it creates a sense of ummah and presence.
Constraints improve design
Avoiding noisy visuals and generic SaaS patterns led to a more thoughtful interface.

On the technical side, I deepened my understanding of:

Embedding and managing live meeting systems
State-driven UI for async approvals
Designing for latency, waiting states, and human pacing

How the Project Was Built

Awliyah was designed as a frontend-first product, focusing heavily on flow and experience before backend complexity.

Core Architecture (Conceptual)

Frontend: Component-driven UI with reusable shells and calm design tokens
Map: Mapbox for global room discovery and interactive availability pings
Live Sessions: Jitsi Meet embedded for reliable, privacy-respecting 1:1 calls
State Management: Local mock state to simulate:
- Room availability
- Join requests
- Approval flows
- Session lifecycle