5 MIN READ

Why we built Zaboor, a digital Urdu hymnal

We built Zaboor because finding a hymn in a printed book takes longer than the first verse lasts.

The idea arrived on a Thursday evening in September 2025, during a service of the Church of Pakistan in Kuwait, and it arrived as an irritation rather than an idea.

The Zaboor home screen beside a five-star Google Play review
Zaboor today, and one of the reviews

In short

  • Zaboor is a free hymnal app for iPhone and Android by Dusk Enterprise: 150 Psalms and more than 300 hymns and geets, in Urdu, Punjabi and English.
  • Every song carries Roman Urdu next to the Urdu script, so people who speak Urdu but don't read the script can sing along.
  • It works fully offline, carries no ads, and is past 25,000 downloads.

Why did we build Zaboor?

We built Zaboor because a hymn number gets called out and the room stops singing to go and find it.

In an ordinary service, a number is called. Pages start flipping. People lean across to see where their neighbour landed, and two or three share a book because they didn't bring their own. By the time most of the room has the right page, the first verse is over. This happens every week, and everyone has quietly accepted it as the price of singing together.

Sitting there, the fix was obvious in the way it probably only is if you write software for a living. Everyone in that room already had a phone in their pocket, and hymns are text. That is the entire problem.

Downloads were never the number we watched, though. A different one told us whether the thing was working, and it later doubled for a reason neither of us thought of.

What two decisions shaped the app?

Two decisions got made that first evening, and both of them turned out to be the product.

The first was Roman Urdu. A large part of the Pakistani Christian community speaks Urdu fluently but cannot read the script comfortably, and that includes both of us. We know the hymns by sound, because we learned them by hearing them. A hymnal in Urdu script alone serves the people who were already doing fine with the printed book, so Zaboor carries both, stacked together, and you follow whichever line you read.

A psalm in Zaboor, Urdu script above its Roman Urdu transliteration
URDU SCRIPT WITH THE ROMAN URDU DIRECTLY BENEATH IT

The second was no ads, ever. Zaboor has never made money and was never meant to. Putting an advertisement between a person and a hymn, during worship, would have broken the one thing it exists to do. Neither decision was a business decision. That is precisely why we could make them.

It wasn't even called Zaboor at first. The working name was Geet, the everyday word for the songs. It changed before launch, but open the app today and the second collection is still گیت.

The original prototype splash screen carrying the app's first name, Geet
THE ORIGINAL NAME, ON THE ONLY BUILD THAT STILL CARRIES IT

What was the hardest part of building a hymnal app?

The content was the hard part, not the interface. Designing the hymn database, entering 150 Psalms and 300-odd hymns, and checking the transliterations line by line is where the six weeks between the idea and the release actually went.

The screens came out of one question: what does a person need in the two seconds between hearing a number called and needing to be singing? So everything is indexed by number, because that is how hymns are called out, and every song carries its page number from the printed book, which lets a congregation use the app and the hymnal at once.

The Zaboor home screen, showing the Psalms, Hymns and Common Prayers collections
THREE COLLECTIONS, BOTH LANGUAGES, AND A CARD BACK TO WHERE YOU LEFT OFF

Because it is all text and all stored on the device, the app works with no signal at all, which matters in a hall with no reception. The honest exception is the worship videos: those are links out to recordings, so that one feature needs a connection when nothing else does.

What happened after we launched?

Zaboor went live on the App Store and Google Play on the same day, 18 October 2025, and grew the way a hymnal grows, one person showing another at church. Twenty downloads, then fifty. The first hundred felt enormous.

The number that actually mattered was daily actives, because watching it pass a hundred meant a hundred real people had opened the app that day, most of them mid-service.

Then we answered every review, which turned out to be the most useful development process we have run. People wrote in asking for geets that were missing, songs their family sang, and those went into the next update. The biggest feature came from outside the two of us entirely: Rev. Clement Maurice, of the Church of Pakistan, asked why each hymn couldn't link to recordings on YouTube, so a person could hear how a song is sung and not only read it. We built it. Daily actives went from around three hundred to around seven hundred after it shipped.

A five-star Google Play review of Zaboor with a reply from Dusk Enterprise underneath
WE STILL ANSWER ALL OF THEM. IT IS WHERE THE FEATURE REQUESTS COME FROM.

The person who knows what an app is missing is usually not the person building it. We learned the same lesson a different way with Cookie Jar.

Where is Zaboor today?

Past 25,000 downloads, around 700 people opening it daily, and 4.8 stars. Still free, still no ads, and still updated whenever somebody tells us a song is missing. It is deliberately not a Bible; for scripture in Urdu, that is Urdu Bible, a separate free app we build.


If your congregation loses the first verse every week, put Zaboor on your phone before the next service and jump straight to the number.

More from Dusk

4 MIN READJUL 25

PDF menu vs 3D menu: which should your QR code open?

PDF menu vs 3D menu: both open from a QR code, but only one shows guests the dish. What changes for guests, for staff, and every time you edit a price.

4 MIN READJUL 14

3-day vs 6-day Push Pull Legs: which should you run?

3-day vs 6-day Push Pull Legs: the 6-day trains each muscle twice a week, which research favours, but only if you attend. Here's how to choose honestly.

4 MIN READJUL 14

How to keep a brag document for review season

How to keep a brag document for review season: one running note, a five-minute Friday habit, and your self-review assembles itself in an afternoon.

3 MIN READJUL 14

How to break a bench press plateau

Break a bench press plateau by checking the log first: most stalls are missed sessions or low volume. Then change one variable and hold it a month.

4 MIN READJUL 14

How to start tracking workouts in 5 minutes

Start tracking workouts in five minutes: log exercise, weight and reps for every work set, then beat one number next session. The whole setup is here.

3 MIN READJUL 14

Push Pull Legs vs Upper Lower: how to choose

Push Pull Legs vs Upper Lower: both build muscle, so choose by how many days you can really train. Here's the research and a ten-second decision rule.

4 MIN READJUL 14

How to start a wins journal in five minutes

Start a wins journal in five minutes: pick one place, write one line about one recent win, and stop. Here's the setup and the rule that keeps it alive.

4 MIN READJUL 14

What counts as a win worth writing down?

What counts as a win worth writing down? Anything that cost you something: effort, fear, or restraint. The size doesn't matter. Here's a simple test.

4 MIN READJUL 14

What is a brag document?

A brag document is a running record of your accomplishments at work, kept so review season doesn't depend on memory. Here's what goes in one and why.

4 MIN READJUL 14

What is a wins journal (and why keep one)?

A wins journal is a record of things that went right, kept so you can reread them later. Here's why it works, and what it does that memory can't.

4 MIN READJUL 14

What is progressive overload? A plain-English guide

Progressive overload means gradually asking your muscles to do more over time. Here's what it means in plain English and how to apply it in the gym.

4 MIN READJUL 14

What is the cookie jar method?

The cookie jar method is a mental technique: collect your past wins and deliberately revisit them when things get hard. Here's how to build yours.

4 MIN READJUL 14

What is training volume, and why do lifters track it?

Training volume is the total work you do in the gym, usually counted as hard sets per muscle each week. Here's why lifters track it and how to start.

4 MIN READJUL 14

Why we built Cookie Jar, a jar for your wins

We built Cookie Jar because every journal we tried demanded streaks and reflection, and we wanted somewhere to keep the good days. Here's the story.

3 MIN READJUL 14

Why you forget your wins (and how to fix it)

You forget your wins because the brain weighs bad events more than good ones, a bias research has measured. The fix: write them down, reread them.

4 MIN READJUL 14

Wins journal app vs notes app: an honest comparison

Wins journal app vs notes app: writing wins down works anywhere, but the point is getting them back on a bad day. Here's an honest comparison.

3 MIN READJUL 14

Wins journal vs gratitude journal: the difference

Wins journal vs gratitude journal: one records what you did, the other what you're thankful for. Here's the real difference and how to choose yours.

3 MIN READJUL 14

Workout app vs notes app: what actually matters

Workout app vs notes app for lifting: what matters is seeing last session's numbers while you train. Here's when notes work, and when they stop.

4 MIN READJUN 1

How a 3D menu changes the way people order

A 3D restaurant menu lets guests see each dish before they order. Across twelve venues, mis-orders fell 31% once people could see what was coming.