Feature scope - proposed scope
WhatsApp Clone Features
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
Feature Set by Role
Four surfaces over one Node.js API, so nothing drifts between the phone, the desk and the console.
The Group
- A name, a photo and a member list, with admins you promote and members you remove. Public groups people can find and join, a size limit you set rather than one imposed on you, replies into a busy thread, emoji reactions, and polls whose votes update live while the group watches.
The Caller
- Voice or video, one-to-one or group, with a proper incoming-call screen and a ringtone that works with the app closed. Every call is logged as missed, accepted or declined with its duration, and the history filters by missed, audio or video.
The Person at a Desk
- The browser client is not a cut-down version. Same conversations, same calls, same stories, same settings, and one account can hold several live connections at once, so a message reaches the phone and the browser together and reading it on one clears it on the other.
The Moderator
- Reported users and reported groups as two queues rather than an inbox, each report showing who filed it, who it names, the reason chosen and the conversation it came from. Block a person or a whole group, and a record of which accounts have already been reviewed so two moderators do not duplicate the work.
The Operator
- Fifteen live dashboard figures, who is online right now and in the last thirty minutes, the mobile and web split, and which sign-in method people actually used, which is how you learn whether to keep paying for SMS. Plus branding, languages and your integration keys, all as forms.
From a Phone Number to a Moderated Community
Seven stages, each one a real part of the build rather than an idealised flow.
A phone number and a one-time code, or email, or Apple, Google and Facebook. There is no user password anywhere in the system, which means there is no password database to steal, and the choice of method is a console setting rather than a build decision.
They find the people they know
- Contact sync shows which of the numbers already on the phone are on your platform, they can save their own name for someone regardless of what that person calls themselves, and they can search for people who are not in the address book at all.
The first conversation happens
- Messages arrive over a persistent socket rather than by polling, so delivery, typing indicators, presence and read receipts are events rather than refreshes. The content is end-to-end encrypted, which means it is unreadable in transit and sits in your own database as ciphertext.
Media goes in the same pipe
- Photos and video from camera or gallery, voice notes recorded in the app, documents, GIFs, a location pin and a contact card. Video is compressed and thumbnailed on the phone before upload, so sending stays quick on a poor connection rather than only on a good one.
A group forms and gets admins
- One-to-one chats and groups are the same object with a flag, so delivery, permissions, moderation and retention behave identically for both. Nothing had to be built twice, and nothing behaves unexpectedly in a group because somebody forgot a case.
Somebody behaves badly, and you can act
- A report arrives in the right queue carrying the reason chosen from a list you wrote, who filed it and the conversation it came from. You block the account or the whole group, and the review state is recorded so the next moderator does not start again from the beginning.
- An hourly scheduled job removes stories past twenty-four hours and pins that have reached their expiry, so ephemeral content genuinely disappears rather than accumulating quietly in the database for years.
Every Feature Earns Its Place
Each row is here because a messaging platform stops working without it, not because a competitor lists it.
The Technology Behind the Features
Deliberately ordinary, so any competent Node and Flutter team can take it forward without us.
A single Node.js application owns every rule and the four clients are presentation layers over one API. One deploy, one schema, one set of rules, which is what stops four surfaces drifting apart over a year of changes.
Boundaries we state in writing for your build
None of these are gaps. Each is a decision about what belongs in a platform and what belongs to the operator running it.
End-to-end encrypted messaging is delivered with the platform. What sits outside it is the operational layer around the keys: encrypted chat backup and restore across a device change, and a recovery path for somebody who loses their phone. Both are scoped work, and both matter more the more your users rely on you.
No payments or subscription billing
- A messenger does not need one, and the right provider depends entirely on your market. If you intend to charge for access, run paid tiers or move money between users, that is an integration quoted against your market rather than a switch somewhere in the console.
The pre-launch hardening pass
- TLS termination, global rate limiting, upload size and type restrictions, secret vaulting, security headers, restricting who can reach the operator console, and a backup restore that has actually been tested. Scoped work we complete with you before the platform faces the public.
Four things you grow into
- Wiring a real-time adapter so several application servers fan messages between themselves, moving media onto object storage with signed URLs and a CDN, append-only audit logging forwarded into a SIEM, and outbound webhooks for bots and integrations. The groundwork for the first two is already in the build.
What is built is real
- Four surfaces over one API, end-to-end encrypted messaging, WebRTC calling with relay fallback, twelve message types, stories with genuine expiry, moderation queues for users and groups, sixteen translated languages with right-to-left, fifteen dashboard metrics, and a documented security posture with a VAPT compliance reference.
- The documentation set that comes with it is written for your engineers rather than for us: product requirements, the data model, an API reference, a developer and security handbook, and the compliance reference above.
More pages on this build
Five pages describing this proposed build. You are on Features.
Four surfaces. One API. Your name on all of it.
iPhone, Android, browser and an operator console over one Node.js application, with the branding, the languages, the limits and the rules all held as configuration you control.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by WhatsApp .
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com