Content sources and attributions
All religious content in the app rests on identifiable sources. For the sake of transparency we list every one of them here.
Qur’an, translation and tafsir
Verse text, translations, tafsir, search and account sync
Turkish surah introductions and translation metadata
Translation catalogue and recitation audio
Translation files (jsDelivr quran-api)
Hadith texts (TR/EN/AR; collection + number)
Multilingual translation catalogue
Turkish translation catalogue
Turkish tafsir texts (al-Mukhtasar, al-Sa‘di, Ibn Kathir; linked from Fawaz README)
- Al-Nuqta
Word morphology and root data
Qur’an text search
- Qurani.ai
Semantic search and recitation recognition
Hadith and catechism
- Riyad as-Salihin — Imam al-Nawawi
Hadith collection. The Arabic text and Turkish translation were taken from an open-source compilation (HasanEksi) and edited.
- Büyük İslâm İlmihali
Source text for the catechism module, organised into twenty-six chapters and two hundred sixty-eight sections.
Litanies
Source and edition details are also shown on each litany’s own page inside the app.
Text from the Mahmud Sami Ramazanoğlu edition; Arabic text and Turkish translation via İslam ve İhsan (Erkam Publishing).
- Hizb al-Bahr — attributed to Abu al-Hasan al-Shadhili
A classical litany of the Shadhiliyya tradition.
Prayer times and location
Primary source for prayer times
- Local astronomical calculation
Fallback used when the primary source is unreachable
- Google Maps Platform
Address and coordinate resolution
Fallback reverse geocoding
Technical infrastructure
Authentication, database and server functions
- Google AdMob
Advertising (excluding Qur’an screens)
- Google Gemini
AI text generation
- Expo Notifications / Firebase Cloud Messaging
Push notification delivery
- Google Play Billing
In-app purchases and subscriptions
Hosting for this website
Classical texts remain subject to their own copyright and publication terms. Listing a source here does not imply that it endorses the app. If you believe an attribution is wrong, please write to us and we will correct it.