PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Feature scope - proposed scope

X Clone Features: Membership Is the Hard Part

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

Six people meet the same account record, through the same REST surface.

The Free Member

  • The full conversation surface: a composer covering text, images, video, audio, GIFs, polls with timed expiry, quote posts and threads, with scheduling and content warnings. Timelines resolve into For You, Following and Bookmarks, with per-member preferences deciding the default rather than a fixed order.

The Verified Account

  • Verification is granted rather than detected. A request enters a review queue, an operator approves it, and the badge is written to the member record with a reason recorded and an audit entry naming who did it. Every client reads the same state, so the badge is consistent on web and mobile.

The Creator

  • Creator subscriptions held as subscriber ids on the creator's own record, which makes a paid following a first-class relationship the platform can count and settle against rather than a payment log sitting off to one side. Tips work on any post or profile, and both settle between two members.

The Correspondent

  • Direct and group conversations carrying audio messages and reactions, read receipts through readBy arrays and live typing through a typingUsers map, over a graph of follows, lists holding member ids, and blocks and mutes stored as explicit records with privacy preferences on the account.

The Operator

  • Fifteen console pages on an authentication path separate from member accounts: verification review and badge assignment, account status control with recorded reasons, suspend, ban and restore, the report queue and its five actions, appeal review, the audit log viewer and sign-in history.
  • One contract across three clients means an entitlement is either true everywhere or false everywhere. That is what stops the failure this category is full of: a paid feature working on the website and not in the app, or a suspension taking effect in one client and not the other.

How It Works, End to End

The path an account takes from arriving to paying, with what gets written at each step.

The account is created

  • Firebase Authentication with email, password and Google sign-in, verified through Admin SDK token checks in middleware rather than trusted from the client. The member record is created carrying the tier, the verification state, the account status, the preferences and the counters that every surface will read.

They use the free tier

  • The full composer and all three timelines, direct and group messaging, search across posts and people, hashtag trending and saved searches. The free tier is a choice you make rather than a limitation you are stuck with, because what it includes is configuration rather than what happened to get built.

Somebody sends a tip

  • A one-off payment on a post or a profile, settling between two members. It asks no commitment from either side, which is why it is usually the first line to show revenue on a young network and the first thing an operator switches on.

An account upgrades

  • The plan moves on the member record and the server begins allowing what that tier permits. Because the check runs before the gated action rather than inside the interface, the upgrade is real in the API, in the browser and in the Flutter client at the same moment.

A badge is requested

  • The request enters the verification review queue in the operator console. An administrator approves or declines it, the decision carries a reason, and an audit entry records who made it. The badge is then written to the member record where every client reads the same state.

A creator starts earning

  • Subscriber ids attach to the creator's own record, so a paid following is a relationship the platform can count and settle against rather than a receipt filed elsewhere. The operator takes a share of a transaction it does not have to fund.

Something has to be enforced

  • A report enters a queue as a record to work rather than mail to read, and closes through hide, unhide, delete, suspend or ban. Status changes carry a written reason, which is what gives an appeal something to examine, and every privileged action writes an audit entry.
  • Sign-in history runs underneath all of it, capturing IP, user agent, device, browser, location, timestamp and whether the attempt succeeded, which is the evidence a support desk needs the first time an account is disputed.

Every Feature Earns Its Place

Each row is here because a membership network stops working without it, not because a competitor lists it.

Underneath sit twelve Cloud Functions, Firestore security rules and composite indexes built for the timeline, search and notification queries specifically.

The Technology Behind the Features

One contract across three clients, on a managed backend a small team can actually operate.

The operator console is deliberately absent from the mobile app. Reviewing a verification request or judging a report needs a screen with room for context rather than a phone.

Boundaries we state in writing for your build

Named here rather than discovered after the invoice.

What does not arrive is people

  • No codebase supplies the thing a social network actually runs on, and a vendor who lets you believe otherwise is selling something they cannot deliver. What arrives is a network whose membership machinery is finished rather than sketched. Who joins it is yours to bring, and it is the slow part.

Live audio rooms are an extension

  • The Firestore rules define a spaces collection, but the surface on top of it is a scoped extension rather than a switch. If audio rooms are part of what you are selling membership for, say so on the first call, because it is real work rather than a setting.

Two-factor fields exist but are not enforced

  • The account record carries two-factor fields. Enforcement is not switched on in an initial scope, which on a platform charging members and holding payment relationships is worth scheduling early rather than discovering during a security review.

What is built is real

  • Three tiers enforced server-side, a verification workflow with recorded reasons, creator subscriptions and tips settling between members, account status control with appeal review, an audit entry on every privileged action, sign-in history with device detail, 64 handlers under one envelope, and a fifteen page console on its own authentication path.
  • Clone is the industry term for software written to work like a product people already recognize. It names the functional target rather than the provenance of the code: this is an original implementation on Next.js, Flutter and Firebase, with no affiliation to, connection with, sponsorship by or endorsement from X or Twitter.

Grant yourself a badge and watch it travel

Open the member and operator logins, approve a verification request from the console, then reload the member profile. Watching a badge move from a review queue to an account record is the quickest way to understand the membership layer.

More pages on this build

Five pages describing this proposed build. You are on Features.

Own the account, not just the feed

The entitlement logic, the verification workflow and the payout relationships transfer with the source, so nobody upstream can reprice your tiers, redefine what a badge means, or take a percentage of what your members pay you.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by X .

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com