Work / Public website

Naseebi — Website

The public introduction to the matchmaking product.

naseebi.com presents Naseebi as a marriage and matchmaking site for people and families: verified profiles, private messages and calls, and family involvement.

Naseebi sign-up screen asking for an email address, with Get OTP, Continue with Google, and Continue With Phone.
Supplied website screen. Sign up.
Problem
People need a public explanation of the product before they install the app or create a profile.
Intended users
Adults looking for marriage, and families who take part in that search. The public page states this; it does not publish user counts.
Role
A website repository was not in the local workspace, so this page does not assign a personal engineering scope to the site.
Implemented scope
The live page at naseebi.com/en. It is a separate case from the React Native app, which has its own repository and store listings.

Workflows

  1. The English homepage introduces matchmaking, private conversation, and family participation.
  2. The page answers public questions about dating versus marriage, cost, family involvement, verification, and privacy. Those answers are marketing copy, not an inspected implementation.

Architecture

  1. 01

    Public website

    naseebi.com/en introduces the product. The page source was not in the local workspace.

    Responsibility
    Explain the service before install
    Concern
    Marketing copy is not an implementation claim
  2. 02

    Mobile app

    The installed client is a separate React Native repository and a separate case study.

    Responsibility
    Carry the in-product flows
    Concern
    Do not treat the site and the app as one codebase
  3. 03

    API

    An Express API repository sits beside the mobile app. Its commits are under other names.

    Responsibility
    Serve the mobile client
    Concern
    Presence of the API does not assign authorship

Decisions

Website and app are different products

The site has to explain the service. The installed app has to run profiles, chat, calls, notifications, and purchases. Those are separate codebases, so this page does not copy the mobile architecture onto the website.

Public claims are not source code

The homepage says profiles are verified and messages are private. No website repository was available to show how verification or privacy is implemented, so those sentences stay product description.

What holds

Decision
Keep the website case study on the public page, and point implementation detail to the mobile case study where a repository exists.
Failure handling
If a claim on the marketing page cannot be traced to source, it is not repeated as an engineering fact.
Evidence
Fetched from https://naseebi.com/en on 12 October 2026. No local website project folder was found beside the mobile and API repositories.
Status
The public site is live. How much of it one person built is not established by the files inspected.
Limits
No website stack, repository, or personal contribution is claimed. Office addresses and phone numbers on the public page are not repeated here.

Stack

A repository was not available, so no stack is listed.