HealthyNikah: a Muslim marriage app rebuilt and relaunched on both stores

The community worked, but the product behind it was holding it back.

• Old code: an Ionic and Angular app with no tests, no monitoring, no automated releases and no safe place for keys.
• Billing bugs: the custom subscription system kept breaking, and some members were charged twice.
• Community rules: guardian (wali) consent, family contacts, a blurred photo view and paid match requests.
• Members to move: more than 3,200 people kept in spreadsheets had to arrive with their profiles filled in.

Decisions that shaped the project:

1. Rebuild the current app properly first. New ideas wait until after the relaunch.
2. Replace the custom billing with RevenueCat instead of patching it again.
3. Move the backend to the client's own AWS account and fix what the security audit found.
4. After launch, work in fixed support blocks, so the client pays for fixes and growth one step at a time.

• Profiles filled in: members found their details already in place.
• Credits kept: unused match credits moved over with them.
• First month free: for members who were already paying.
• Log in to activate: a moved profile stays out of the feed until its owner signs in.

• Sign-up: a few short steps with an 18+ age check, a profile and country of residence.
• Membership: a joining fee and a subscription that starts billing later.
• Credits: each match request costs a credit, and members can top up.

• Feed: search and filters sit right in the main feed, with pull to refresh.
• Profile code search: find the exact person whose code someone shared with you.

• Guardian (wali) consent: built in, as the community expects.
• Family contacts: required on women's profiles.
• One-time blurred photo view: pictures stay private.

• Notifications: push messages and email.
• Admin panel: the client's team manages members and the platform.

The biggest risk was Apple review. Apple first rejected the app as one more dating app in a crowded category, even though it is built for marriage and an earlier version had passed. We removed the dating language, appealed to Apple and sent a new build. The guardian consent feature passed review on the way, and the app was approved on 29 May 2026.

Billing was the second risk. The custom subscription system kept failing, so we stopped patching it. Payments moved to RevenueCat, connected to Apple and Google in-app purchases, with Stripe for payments outside the stores. That ended the recurring billing bugs of the old system.