Why we built Urdu Bible, a Bible in two scripts
Two people in the same family cannot read the same Urdu Bible. That is the problem the app exists to solve, and it is a layout problem before it is anything else.
The grandparent learned Nastaliq in Pakistan and reads it fluently. The grandchild, schooled in English, speaks Urdu and cannot decode a line of the script. Hand them one book and one of them is a spectator.
In short
- Urdu Bible pairs the Urdu script with a Roman Urdu line on every verse, so two readers with different scripts stay on the same words.
- The obvious way to build that is the way we rejected, and rejecting it decided the rest of the app.
- Carrying two lines per verse has a specific cost, paid in the one resource a phone screen never has enough of.
What problem was Urdu Bible built for?
It was built so that a reader of the script and a reader of Latin letters can sit with the same verse at the same time.
That is a narrower goal than "an Urdu Bible app," and the narrowness is the point. Complete Urdu Bibles already exist. What did not, as far as we could find, was one where neither reader waits for the other or holds a different book.
The situation is ordinary and not going away. A large part of the Pakistani Christian community speaks Urdu fluently without reading Nastaliq comfortably, through English-medium schooling and through growing up abroad. We wrote about those readers in why can't I read Urdu even though I speak it.
What was the decision that shaped the app?
We rejected the toggle. The obvious build is a script switch in the settings: read Nastaliq, or read Roman, flip when you like.
A toggle serves one person at a time. It solves nothing for two people sharing a screen, because at any moment the app shows one script and excludes whoever cannot read it. Two separate editions are worse: the family owns two books again, which is where we started.
So the two scripts had to be simultaneous and aligned per verse, not per chapter and not per app state. Every verse carries its Roman line directly beneath it, permanently, with no setting to get wrong.
That single decision then wrote most of the rest of the app. If both lines are always present, the screen has no room for anything else, which is why the reading page is the whole product.
What did that cost?
Vertical space, which is the resource a phone has least of. Two lines per verse means roughly half as many verses on screen as any single-script Bible app, and Nastaliq makes it worse, because it descends through each word and needs more room per line than a Latin face does.
So Urdu Bible shows less at once than its competitors, deliberately, and no version of the design avoids that. A verse you can actually read beats two more you cannot, but it is a real trade and anyone comparing screenshots will notice.
It also decided the offline behaviour, though that one was easy. The Bible is a fixed, finite text, so there is no argument for fetching it: bundling all 66 books costs a larger download once and then nothing. That reasoning is in what is an offline Bible app.
What was actually hard to build?
The Roman line, verse by verse, across all 66 books. The reading screen was a week's work; the text was the project.
Roman Urdu has no standard spelling, so every transliteration is a judgement about how a word is most likely to be read aloud by someone who has never seen it in Latin letters. There is no authority to check against and no automated conversion that gets it right.
This is the same shape of problem we hit building our hymnal, where entering and checking 150 Psalms and 300-odd hymns was where the six weeks went; that story is in why we built Zaboor. The lesson we carried across is that content work does not compress: you cannot ship the interface early and fill the text in later, because the text is the product.
The honest limitation is that the Roman line stays imperfect. Latin letters cannot distinguish some Urdu sounds, so a spelling occasionally maps to more than one word and the reader resolves it from context.
FAQ
Is the Roman Urdu line a translation of the Urdu?
No. It is the same Urdu words respelled in Latin letters, so both lines are one sentence written twice. Nothing on the page is a translation of anything else on the page; we set that out fully in transliteration vs translation.
Why not let readers choose one script instead of showing both?
Because a choice serves one reader at a time. The app exists so that two people who read different scripts can follow the same verse together, and a toggle re-creates the problem it was meant to remove.
Did you translate the Bible into Urdu yourselves?
No. The Urdu text is an existing Urdu translation of the Bible, set as it stands. What we added is the typesetting and the Roman Urdu line beneath each verse.
If your family reads in two different scripts, Urdu Bible puts all 66 books in front of both of you at once. Free, offline, no ads.
