MatrimonyIndiaLaunched in 15 days

Community Matrimony Platform - India

How we built and launched Rawa Rajput Matrimony, a trusted matchmaking PWA for one community, in a form any family can open from a WhatsApp link.

Rawa Rajput communityLate September 2026Architect and technology lead

Illustration of families connecting through a private community matrimony app on their phones

Overview

The Rawa Rajput community had no dedicated, trusted place to find matches. Families relied on word of mouth, relatives and general matrimony sites built for everyone. The brief was a matchmaking platform for this one community: trusted, private and easy for anyone to open from a shared link.

Technologies Used

Next.js

TypeScript PWA frontend

Node.js

One REST API for every client

Redux Toolkit + Saga

State and background sync

Firebase Auth

Linked email, Google and password reset

Fast2SMS

Mobile OTP login

Firebase Cloud Messaging

Push alerts

Encrypted IndexedDB

Fast, private on-device cache

JWT

Secured API calls

The Challenge

General matrimony sites did not support the community's matching rules, offer enough trust and moderation, protect sensitive contact details, or fit how families share information on WhatsApp.

Matching rules they do not support: gotra exclusions, manglik status and native-village details are crucial factors, not optional filters.
Low trust: open sites mix in profiles from outside the community, with little moderation.
Privacy worries: phone numbers and addresses can be too easy to reach. Families expect tight control over who sees photos and contact details.
The wrong channel: requiring an app-store install adds friction for parents and older relatives who share everything on WhatsApp.

Families searching for matches through relatives, word of mouth and generic matrimony sites that don't fit the community

The Approach

I owned the technology end to end: architecture, feature scope, security and privacy, and delivery through the late-September 2026 launch.

A PWA, not a store app
A profile link shared on WhatsApp opens instantly in the browser, with no install needed. Users can add it to their home screen in one tap. Fixes go live the same day, with no store review and no old app versions to support.
Login the way people already sign in
Users register with their mobile number and an OTP. Each account is also created in Firebase so mobile OTP and email/password can be linked to one account. Linked Gmail accounts can use Google sign-in; password recovery works through Firebase.
Matching built around the community's rules
Profiles hold gotra, manglik status, family details and native village. Partner preferences support gotra exclusions alongside age, height, income, education and location. Search shows active, non-blocked profiles of the opposite gender by default.
Public for discovery, private for contact
Visitors can search and view public profiles without signing up, and those pages can be indexed by Google. Phone numbers, email, address and horoscope details stay behind login and the paid plan.
Engagement that mirrors how families decide
Likes, interest requests that can be accepted or declined, shortlists, profile-view and contact-view history, and push alerts support the way families make decisions.
Safety and moderation built in
Users can block others, and blocked users cannot see or contact each other. Admins verify KYC documents, moderate photos and handle abuse reports. Admin accounts cannot be created from the app.
Fast and private on shared phones
Data is cached in encrypted IndexedDB, so the app loads quickly and stays unreadable if a family phone is shared. Background sync retries actions when the connection returns.

Architecture

The PWA talks to one REST API over JWT-secured calls. Only the backend sends push notifications and OTPs. Every user loads the same latest version, so there is one API version to maintain.

Trade-offs We Made

Decision	What we gained	What we gave up
PWA instead of native apps	Instant access from shared links, same-day releases and one codebase.	No App Store or Play Store listing; fewer device features on iPhone.
Public profiles, private contact details	Google traffic and easy browsing for families.	Some profile details are visible to non-members, so moderation matters more.
Mobile OTP first, with an email account linked behind it	Familiar sign-up for every age group, plus a fallback login.	Extra work to keep Firebase and backend accounts in sync.
One community only	Higher trust and matching rules that fit.	A smaller audience by design.

Results & Impact

Rawa Rajput Matrimony went live in late September 2026, with no app store approval to wait on.

Rawa Rajput Matrimony installed on a phone home screen as a PWA, with no app store needed

Registered profiles

500+

First 15 days

Verified (KYC-approved) profiles

300+

First 15 days

Average profile completion

80+

As of today

Interests sent

800

First 15 days

App store dependency

None

PWA, installable from the browser

Business Impact

Went live with no app store approval to wait on

500+ profiles registered in the first 15 days

300+ profiles KYC-verified in the first 15 days

800 interests sent in the first 15 days

Fixes ship the same day, with no store review or old app versions to support

Public profiles are indexed by Google, bringing families in through search

Where This Pattern Applies

The same architecture fits any trust-sensitive community platform, wherever it runs. Diaspora networks in the UK, the Gulf and Africa, faith or professional communities, and alumni groups share the same needs: closed membership, shared-link discovery, strong privacy and moderation.

What changes by market is mostly compliance and channels: GDPR in Europe, PDPL in the UAE and Saudi Arabia, POPIA in South Africa, NDPA in Nigeria and the DPDP Act in India. Arabic and right-to-left layouts matter in the Gulf too.