Worked as the backend-focused developer in a seven-person team building a matching platform. Built the Django backend, REST APIs, PostgreSQL database, authentication, matching logic, notifications, admin panel and deployment, with additional frontend and Flutter work.
- Role
- Backend-focused Full-Stack Developer
- Timeline
- 2024 — 2025
- Platforms
- Web, API, iOS, Android
- Status
- Shipped
Why it was built
MehramMatch was built to bring the traditional Muslim matrimonial process into an online platform while still supporting the role of matrimonial agents. The system needed to handle detailed user profiles, religious and family information, partner preferences, profile discovery, interests, shortlisting and messaging, while giving agents a separate way to manage and assist users.
What went into it
Built the Django backend and REST API layer serving the application's profile, authentication, matching, interest and user-management workflows.
Implemented the user journey from registration and OTP-based authentication through multi-step profile completion, profile discovery, filtering, interests and shortlisting.
Built support for matrimonial agents who could manage multiple users, view activity and switch between agent and user contexts when assisting clients.
Implemented real-time communication using Django Channels and Redis, connecting the messaging experience with the backend.
Worked directly with PostgreSQL, JWT authentication, API integration and production deployment, while also contributing to the React web frontend and Flutter mobile application.
Technical decisions
- 01
Used Django and Django REST Framework as the central backend layer so the same API could serve the application's client interfaces instead of duplicating business logic across platforms.
- 02
Used PostgreSQL for the application's relational data, covering users, profiles, preferences, interests and agent-related information.
- 03
Used JWT-based authentication for API access, allowing authenticated clients to send bearer tokens with requests across the application.
- 04
Introduced Django Channels with Redis for real-time communication instead of relying entirely on traditional request-response APIs for chat functionality.
- 05
Modelled the platform around both individual users and matrimonial agents, allowing agents to manage multiple users while maintaining separate agent and user contexts.
- 06
Kept profile creation as a multi-step process because the platform required significantly more information than a typical basic account, including religious details, family information, education, career and partner preferences.
Outcome
The result was a multi-platform matrimonial system connecting user profiles, partner discovery, interests, shortlisting, agent-assisted workflows and real-time messaging through a shared Django backend. The platform supported both individual users and matrimonial agents, with the backend providing the common API and data layer for the application's clients.
Built with
Have something you need built?
Whether you're starting something new or need help with an existing application, tell me what you're trying to build and where things currently stand.