Dawn
Prayer times and a daily plan orient the day.
2026 / Independent product · Ramadan companion
live
Hilal
A bilingual, RTL-aware habit companion designed for the rhythm of Ramadan.
01
The ritual
A product paced by the day and the month.
Hilal gathers the routines of Ramadan into one bilingual companion. The experience is structured around return: orient the day, act with intention, see progress, and continue without losing the larger month.
Day
Habits, fasting progress, Quran, and reflection stay close at hand.
Dusk
The day resolves into visible progress rather than a noisy score.
Month
Calendar, streaks, achievements, and rewards preserve continuity.
The calendar is not administration. It is the emotional spine of a finite, meaningful month.
Daily surfaces put the immediate ritual first while progress views reconnect each day to the full Ramadan arc. Rewards support continuity, but the primary visual language remains reflective rather than competitive.
Responsive layouts preserve that hierarchy from a broad dashboard to a mobile-first, installable experience.
02
Localization
Arabic is a first-class layout, not a translation layer.
Hilal supports Arabic RTL and English LTR presentation. Direction affects reading order, alignment, icon relationships, navigation, and the rhythm of dense information—not only the strings.
العربيةرحلة رمضان، بإيقاعك.
واجهة تتبع اتجاه القراءة وتضع الصلاة والعادات والتقدم في سياق مألوف.
EnglishYour Ramadan, in rhythm.
The same information architecture adapts to reading direction without demoting either language.
03
Engagement system
Rewards add warmth to consistency.
Companions, lanterns, themes, patterns, badges, decorations, and titles form a layered reward system. Unlocks personalize the experience while keeping the underlying habit record understandable.
04
Frontend architecture
A local-first PWA with resilient daily utilities.
The documented build uses Next.js, TypeScript, next-intl, motion, service-worker capabilities, and browser storage. Prayer time, Quran, and Hadith integrations are designed with cached and fallback paths so the daily experience does not depend on a perfect connection.
01 / Direction
Locale controls the whole interface.
RTL/LTR behavior is treated as a layout concern across navigation, content, and responsive composition.
02 / Resilience
Daily context remains useful locally.
PWA behavior, cached resources, fallbacks, and local persistence support repeated use beyond a single connected session.
03 / Privacy
Personal progress stays on the device.
The documented implementation protects locally persisted product data with browser cryptography rather than requiring an account for the core ritual.