I Built an App for 1.8 Billion Muslims and Learned More About Retention Than From Any SaaS

What twelve months of building a Quran app taught me about niche markets, anxiety-driven messaging, localization that actually matters, and why every SaaS playbook I'd read was wrong for this audience.

The moment SaaS playbooks broke

Last year I shipped a Quran app called QuranWay. iOS only. Solo dev. Built it because I noticed the existing apps in the category were either feature-heavy and ugly, or pretty and shallow. None of them respected the user the way I'd want to be respected if I were the user.

I'd read every SaaS playbook on the internet by that point. Hooked. The Mom Test. Lenny's newsletter. Every retention deep-dive, every onboarding teardown, every "10 things I learned shipping my first $10K MRR app" thread. I had the spreadsheet of metrics ready. I knew my activation funnel, my trial-to-paid conversion target, my D30 retention benchmark.

None of it worked the way the playbooks said it would.

Twelve months later, I'm still building QuranWay, but I've thrown out 80% of the rules I started with. Here's what twelve months in a religious niche taught me about product, marketing, and retention that no SaaS post will ever tell you.

The niche is bigger than your TAM model assumes

There are 1.8 billion Muslims in the world. Roughly one in four humans alive. The serious Muslim app market is dominated by maybe four apps you've heard of, and the long tail is a mess of half-finished projects, ad-stuffed wallpaper-grade junk, and Quran reader apps that haven't been updated since 2019.

If you come from B2B SaaS, the first instinct is to immediately segment. "Practicing Muslims in the US." "Converts learning Arabic." "Hajj pilgrims." Yes, those segments exist. But the niche has a feature most SaaS niches don't: a shared identity that creates near-universal demand for something in the category, even from people who never download a paid app.

That changes the math. Your distribution problem isn't "find users who care about your features." It's "find users who haven't yet found a version of your app they trust." The ceiling is enormous. The floor — meaning what they'll pay for — is much lower than you'd assume. Both of those things are true at the same time, and both of them require a different playbook.

Lesson 1: Anxiety, not features

The single most expensive mistake I made was launching with a feature-led onboarding.

You know the kind: three sliding screens, each with a hero illustration, each saying something like "Track your daily readings" or "Get prayer reminders" or "Beautiful, ad-free reading experience." It's the default for every well-designed app I'd ever used. So I copied it.

It bombed. My paywall-to-conversion was 0.58% lifetime. Seven paid conversions out of 1,200 paywalls served. Effectively nobody was buying.

I spent a long time looking at the funnel before I understood the problem. People weren't downloading my app because they wanted features. They were downloading it because they were carrying a feeling — sometimes guilt, sometimes grief, sometimes longing, sometimes just the quiet pressure of a calendar moment like Ramadan or Hajj. The features were what I was proud of. The feelings were what they arrived with.

Two weeks ago I shipped a rewrite of the entire onboarding. Instead of "Track your readings" the first screen now says something close to: "There are moments when you need this app. Let it be ready for them." No feature pitch. No screenshot of the prayer tracker. Just an acknowledgement that the user is carrying something.

It just landed in Apple review. I don't have the numbers yet. But I already know the directionality is right, because every test reader I sent the new flow to said some version of "okay, I get what this is for now." Nobody said that about the old flow. They'd say "looks clean." Nobody said "I get what this is for."

If you're building for a faith or wellness audience, your onboarding is not a feature tour. It's an acknowledgement of why they showed up. Skip the acknowledgement and the rest of your funnel is a leaky bucket.

Lesson 2: Localization is not optional

Every SaaS playbook says: launch in English first, validate, then translate.

In a religious niche, that advice is wrong. The serious users of a Quran app are not English-first. They're Arabic, Urdu, Bengali, Persian, Indonesian, Malay, Turkish, French, German. If your app launches English-only, you're invisible to two-thirds of the addressable market on day one, and the App Store search algorithm reads your metadata, screenshots, and reviews against the user's device locale. English-only metadata in a non-English locale gets you nothing.

I shipped QuranWay localized into fourteen languages on the IAP layer (the part that shows the price and trial), plus localized App Store screenshots, keywords, and promotional text for each. Three hundred and ninety App Store assets. Generated overnight with a Codex GPT Image 2 pipeline because there was no way I was paying a localization agency on indie-dev money.

Here is the thing nobody warns you about: Apple App Store Connect does not accept Urdu, Bengali, or Persian as App Store locales. Those are three of the largest Muslim populations on earth. You can ship Urdu strings inside your app via Localizable.strings, but you cannot ship Urdu screenshots or Urdu keywords on your store page. That's a hole in Apple's storefront that affects roughly half a billion potential users in a single niche.

The workaround is to localize what you can (the in-app experience) and aim the App Store metadata at the languages Apple does accept (Arabic, Indonesian, Malay, Turkish). The first time a Pakistani user opens your app and finds the strings in Urdu after downloading from an English store page, the conversion is higher, not lower, because the experience felt unexpected and respectful.

If you're building for any global niche, do not launch monolingual. The cost of translating IAP strings into fourteen languages once, with idempotent scripts, is hours of work. The cost of being invisible in the App Store of two-thirds of your market is your business.

Lesson 3: Conversion is broken without trust

Last month I ran a small Apple Search Ads campaign on six keywords. €21.41 spent over a week. 48 installs. Zero paid conversions.

Zero is a depressing number when you're looking at a spreadsheet, but it's an interesting number when you're trying to learn. €21.41 is not a media-buy. It's diagnostic. It tells me my app acquires (people install when they see the ad), but does not convert (none of them subscribe inside the trial window). Acquisition was working. Conversion was the broken link.

I went into the funnel after the campaign and the cause was clear. People were installing, opening the app, getting hit with the old feature-led onboarding, getting taken to a paywall that read like every other subscription app on the planet, and bouncing. The acquisition channel was fine. The product surface they landed on was the issue.

This is the part where SaaS playbooks lead you astray. The default advice is to A/B test the paywall. Try different prices. Add a "skip" button. Run a discount cohort. Those are all real levers. But they don't fix the actual problem when the user doesn't yet trust that you understand them. You can show a paywall with a 70% lifetime discount and a Persian rug background and still get zero conversions if the previous three screens screamed "this is a generic subscription app."

Trust comes from the surface area before the paywall, not the paywall itself. I had to rewrite onboarding before retuning the paywall would even make sense. We'll see in 30 days if the new flow turns acquisition into actual revenue. But the lesson is general: in a faith or wellness niche, the paywall is downstream of trust, not upstream of revenue.

Lesson 4: Retention is not engagement

Every SaaS retention playbook has a section on streaks, push notifications, daily reminders, "open the app every day" gamification. Calm has it. Duolingo has it. Half the productivity apps on the App Store have it.

For a Quran app, that pattern is poisonous.

Spiritual practice is not a streak. The relationship the user is trying to build is not with your app. If you push them daily reminders that they "broke their streak," you are inserting your brand into a moment of guilt they did not ask you to participate in. They will not thank you for that. They will delete the app and never come back, and they will tell two friends that your app is the one that made them feel worse.

The pattern that works is the opposite. Quiet presence. Respect the silence. Ship features that make the moment they choose to come back meaningful, but never make them feel obligated to come back. My push notifications are limited to prayer times (which they opted into) and Ramadan/Hajj reminders (which match their calendar). No "hey, you haven't read in three days!" Ever.

Counterintuitively, this drives better retention than the streak pattern. Users return because they want to, not because they're avoiding a guilt-trip. The cohort that returns is also the cohort that's most likely to subscribe, because the relationship with the app is positive instead of nagging.

If you're building anything where the user's underlying motivation is identity or values (faith, wellness, learning, parenting), throw out the streak playbook. Your job is not to maximize engagement. Your job is to be ready for the moment they show up, and to disappear quietly when they don't.

What I'd tell another indie dev considering a niche

If you're sitting on a niche idea — religious, wellness, parenting, hobby, language, anything where the user's motivation is identity-driven — here's the four-line playbook I wish someone had handed me a year ago.

Read the user, not the playbook. Your audience does not behave like a B2B SaaS buyer. Treat them like the humans they are arriving as, not the conversion targets your analytics dashboard wants them to be.

Localize on day one. Not because it's nice. Because the App Store algorithm punishes monolingual apps in non-English markets, and your niche is global.

Build trust before pricing. Your paywall is downstream of the four screens before it. Fix the trust surface first.

Ship presence, not engagement. The win condition is that the user feels supported, not that you maximized DAU. Build the app you'd want to use during a moment that matters. That's the only retention strategy that scales in a niche this deep.

I'm still learning. The new onboarding just landed in Apple review last week. The pricing experiments are ongoing. The Hajj 2026 marketing campaign drops next week. If any of this resonates and you want to see how it's evolving, QuranWay is on the App Store — and the chapter on niche playbooks is the one I'm still writing in real time.

Andy Garcia — solo dev, building four iOS apps, one LegalTech SaaS, and writing about what I learn shipping in public. If indie-dev field notes are your kind of read, I have a book about working with Claude as your second pair of hands that picks up where this article leaves off.