Text integrity
Every āyah comes from a public, independently verifiable source
Arabic and translation come from public datasets you can check yourself. Fetched text may also be cached for offline reading; the cache is not yet checksum-verified.
- Arabic and translation come from Quran.com's public API, live.
- Every verse carries its verse key so you can verify it independently.
- Seerah material is graded by the strength of its evidence, never blurred.
Quran.com API (v4)
Uthmānī script (KFGQPC lineage) + M. A. S. Abdel Haleem as the standard translation, fetched per āyah at read time.
Quran.com API (v4) — tajwīd script (text_uthmani_tajweed)
The same Uthmānī text, served with inline tajwīd rule annotations (madd, ghunnah, qalqalah, idghām, ikhfāʾ, iqlāb and the rest of the dataset's rule set). AyaSeerah only colours what the API marks — no tajwīd rules are detected or invented here, and the colour convention is the one the dataset itself specifies.
Quran.com / Quran Foundation Audio API (v4)
Ayah-by-ayah recitation audio (/recitations/{id}/by_chapter) with word-level segment timings. Verse-recitation IDs are kept strictly separate from the chapter-reciter ID space, as the API documents.
Tanzil Project
An independent reference text. A direct character-by-character comparison against Tanzil is not yet part of AyaSeerah's automated checks.
KFGQPC / Madinah Muṣḥaf
The printed reference of record for Ḥafṣ ʿan ʿĀṣim orthography and āyah numbering.
Quranic Arabic Corpus (University of Leeds)
University of Leeds linguistic reference for word morphology, roots and syntax. AyaSeerah's beginner explanations are editorial; links open the Corpus' own analysis rather than representing our explanations as its data.
Don't take our word for it — check an āyah right now
Trust in a Qur'an app should be verifiable, not asserted. This runs the same request the surah pages run.
VERIFY IT YOURSELF
Enter any verse key. Your browser calls the same public endpoint AyaSeerah calls — no AyaSeerah server in between. The request URL is shown so you can paste it into your own browser and compare.
Currently implemented
- Qur'anic Arabic and translation are requested from Quran.com's API by verse key and displayed with the verse reference; the check-an-āyah tool makes a fresh request.
- The reader uses Quran.com's per-word glyph codes with QCF tajwīd fonts; the API's annotated text is the accessible and loading fallback.
- Offline pages and fetched text can be cached. Caching is not the same as checking the cached copy against a checksum.
- Study commentary names its sources; that attribution permits review but is not scholarly certification or proof of every interpretation.
Partially implemented
- Character-level comparison: a standalone maintenance script compares stored verse text with Quran.com (which uses Tanzil-derived text). It does not compare an independent Tanzil file, and a mismatch does not currently block a build.
- Build-time and automated source checks: font coverage and lesson narration checks exist; other verse, tajwīd and coverage audits are runnable separately. There is no mandatory whole-muṣḥaf source-integrity gate in the build or CI.
- Offline text caching: stored text may be read offline, but the cache is not authenticated against a SHA-256 manifest before display.
Planned / future hardening
- Direct character-level comparison with an independent Tanzil text, with any mismatch failing the build. Today's standalone comparison uses Quran.com as its reference, not a separate Tanzil file.
- A generated per-āyah SHA-256 manifest, with per-sūrah and whole-muṣḥaf checksums. No such manifest is generated or checked today.
- Verification of cached or downloaded text against that manifest before display. Stored API text is not currently rechecked with a checksum.
- A mandatory build/CI gate for whole-muṣḥaf verse counts, basmalah and sajdah assertions and independent text comparison. Existing checks do not cover all these claims as a release gate.
What AyaSeerah covers — and what it does not
A plain statement of scope, so you know what this app is for before you rely on it.
IN SCOPE
- Arabic text and translation requested from Quran.com's public API, with the verse key printed for independent checking
- Study in the order of revelation, walked alongside the seerah of the Prophet ﷺ
- Thematic sections, broader revelation context, and specifically reported occasions where sourced
- Root-word vocabulary building across the sūrahs
- Retrieval practice: quizzes, drills, surah and phase exams with sourced answers
- Spaced repetition for meaning and context, not only for ḥifẓ
- Plain muṣḥaf reading with a choice of reciters and translations, offline packs and progress sync
OUT OF SCOPE
- Automated checking or tajwīd correction of your own recitation (the recitation page only records and plays you back)
- Answering a question the written lesson does not already answer, or marking a spoken answer (Teach Me speaks the cited lesson; the written quizzes, papers and drills do the checking)
- Ijāzah, certification or a standing scholarly review board
- Fatwā, rulings or personal religious guidance
- A replacement for your printed muṣḥaf or a qualified teacher
Anything listed as out of scope is simply not part of this app today; use your printed muṣḥaf and your teacher for it.
The questions a careful student should ask
Who reviewed the tafsīr content? Is it scholar-certified?
No — and AyaSeerah says so plainly rather than implying otherwise. The study content is a compilation, not an independent scholarly ruling. Study notes cite classical works (Ibn Kathīr, al-Ṭabarī, al-Qurṭubī, al-Saʿdī, and ḥadīth collections) for readers to check. A historical setting alone is not an authenticated occasion of revelation. Study with a teacher; use this as scaffolding between classes.
Is any Qur'anic text AI-generated or paraphrased?
Never. Arabic text and translation are fetched verbatim from the Quran.com API and rendered as returned; no model writes, completes or corrects a single word of Qur'an. AI is used only outside the text: Listen reads lessons written from the cited study material (mostly recorded in advance), and it can read photos of your handwritten notes if you choose. Teach Me does not answer new questions or mark spoken answers — the written quizzes, papers and drills do the checking, with sourced answers. See the curriculum provenance page for the full account.
What if the API is down or you go offline?
Stored text may be used as an offline fallback and is labelled as such. It is not yet verified against a checksum before display.
How is the revelation order decided — isn't that disputed?
Yes, and the app treats it as disputed. Each sūrah carries a certainty level: mutawātir/ṣaḥīḥ-attested placements (e.g. al-ʿAlaq first), strongly-reported placements, and reconstructions where scholars differ. Where the ordering is scholarly ijtihād (al-Suyūṭī's al-Itqān, Nöldeke-influenced tables, and the Egyptian standard order), that is stated on the phase, not hidden.
Can I report an error?
Yes, and please do. Text errors are checkable in seconds against the printed verse key; content errors are checkable against the cited source. Reported corrections take priority over new features.