Profiles, chat, calls, and subscriptions on the device.
The Naseebi mobile client is an Expo React Native app, bundle com.nuae.naseebi. Local screens cover registration, discovery, chat, voice and video calls, notifications, and subscriptions.
A matchmaking product has to work as an installed app: identity, profiles, private conversation, and calls, not only a marketing page.
Intended users
People using the iOS or Android app. No install or revenue figures are published here.
Role
The local mobile commits I could read are under other names, and the API package names another author. This page describes the repositories. It does not claim sole ownership.
Implemented scope
Expo SDK 53 client, version 3.3.5 in the local app config, talking to a separate Express API. Store listings are the public iOS and Android apps.
Workflows
Registration collects email or phone, OTP, password, who the profile is for, name, gender, birthday, and a photo.
Home, nearby, filters, partners, spotlight, and favorites are the discovery screens in the client.
Chat uses a socket client and a chat screen. Audio and video screens use Agora, with incoming-call handling and notification hooks.
Subscription screens and react-native-purchases are in the client. The API also has Stripe and subscription routes.
Block, report, privacy policy, and account deletion screens exist in the client.
Architecture
01
Expo client
React Native screens for registration, discovery, chat, calls, notifications, and subscriptions.
Responsibility
Run the product on iOS and Android
Concern
Permissions and store builds
02
Identity
Firebase Auth plus Google and Apple sign-in libraries, with OTP and password screens.
Responsibility
Establish the signed-in user
Concern
More than one sign-in path
03
Conversation
Socket.IO chat in the client. Agora for audio and video. Firebase messaging and Notifee for notifications.
Responsibility
Deliver messages and calls
Concern
A call is not just another chat row
04
Express API
Separate Node service with MySQL, S3 uploads, Agora tokens, and Stripe subscription routes.
Responsibility
Persist profiles and authorize calls
Concern
Authorship is not inferred from the folder
Decisions
Calls and chat are different channels
Text uses the socket chat path. Voice and video use Agora tokens from the API, plus notification and incoming-call handlers so a call can arrive while the app is open. The client keeps those paths separate.
Sign-in is more than one provider
The client includes phone OTP, email and password, Google sign-in, and Apple sign-in. Firebase Auth and the API both appear in that flow. A single password form would not cover the screens that exist.
Purchases sit next to the profile, not inside chat
Premium, subscription, and manage-subscription screens are their own routes. The API has payment and subscription routes. The case study does not claim a measured conversion result.
What holds
Decision
Ship one React Native client for iOS and Android, with native modules for calls, push, camera, and store purchases, instead of a second web-only client.
Failure handling
Notification permission, microphone and camera permission, and a dropped call are handled as device states. The page does not claim an offline outbox for this app.
Evidence
Local app config, screen list, and dependencies in NaseebiReactNativeMobile. Route list in Naseebi-Backend. Public store URLs supplied for this page.
Status
iOS and Android store listings exist for Naseebi. The local client version recorded in app config is 3.3.5.
Limits
Commit history does not establish a personal scope. Private repository URLs are omitted. No usage, revenue, or review metrics are stated. The images are supplied marketing artwork. Prices and profile details printed on them are not reported results.