Feature scope - proposed scope
Twitter Clone Features: A Composer Is Not a Product
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 touch a public network. All six call the same REST surface under one API.
The Member
- 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 rather than one undifferentiated feed, with per-member timeline preferences behind that choice.
The Correspondent
- Direct and group conversations carrying audio messages and reactions, read receipts through readBy arrays and live typing through a typingUsers map. Around it sits the graph: follows and followers, lists with member ids, and blocks and mutes stored as explicit records rather than inferred.
The Creator
- Creator subscriptions with subscriber ids held on the creator record, so a paid following is a first-class relationship rather than a bolt-on. Tips move between members directly, and verification badges are granted on approval rather than bought, which keeps the signal worth something.
The Advertiser
- Typed campaigns across promoted post, banner and sponsored formats, each carrying a budget and a daily budget, spend tracked against the cap, and targeting keywords per campaign. An operator reviews campaigns before they run, which is the difference between an ad desk and an upload form.
The Developer
- OAuth 2.0 applications with scopes, a client id, secret and redirect URI, plus SHA-256 hashed API keys issued per user with per-key rate limits. This is what separates a product other people build on from an app that merely has an audience.
The Operator
- Fifteen console pages on a separate authentication path from member accounts: the report queue with hide, unhide, delete, suspend and ban, suspension management with reasons, ad campaign review, verification review, the audit log viewer, login history, and API key and OAuth application oversight.
- Admin authentication is held apart from member authentication, and every privileged action writes an audit entry naming the administrator, the target and the reason. Role granularity beyond that is configuration we scope with you.
How It Works, End to End
They join
- Firebase Authentication with email, password and Google sign-in, verified through the Admin SDK in middleware rather than trusted from the client. Account security begins recording immediately: login history capturing IP, user agent, device, browser, location, timestamp and outcome.
They post
- Text, images, video, audio, GIFs, polls with timed expiry, quote posts and threads, with scheduling for later and content warnings where the post needs one. Every mutation runs an ownership check, so editing and deleting are bounded by who actually wrote the thing.
The timeline resolves
- For You algorithmic, Following chronological, and Bookmarks as a saved feed, with per-member preferences deciding the default. Likes, reposts, quote counts and view and impression tracking are denormalized onto the feed document, so rendering a timeline does not run an aggregation query per post.
They find each other
- Full-text search across posts and people, hashtag extraction with trending, and saved searches per member, all backed by composite Firestore indexes built for those queries specifically. Notifications land in a per-user subcollection covering mentions, replies, follows and likes, paged by cursor.
They talk privately
- Direct and group conversations with audio messages, reactions, read receipts through readBy arrays and live typing through a typingUsers map. Firestore real-time listeners are what make presence and delivery cheap to build correctly rather than a subsystem of their own.
Money starts moving
- Tips between members need no commitment from someone who just arrived. Subscription tiers sit at Free, Premium and Pro with entitlement enforced server-side, creator subscriptions attach subscriber ids to the creator record, and ad campaigns run against budgets with spend tracked to the cap.
Something goes wrong
- A member report enters a queue rather than an inbox and resolves through hide, unhide, delete, suspend or ban. Every resolution writes an audit entry recording the administrator, the action, the target, the reason and the timestamp, and the member can appeal to an operator.
Every Feature Earns Its Place
Each row is here because a public network stops working without it, not because a competitor lists it.
Underneath sit twelve Cloud Functions, Firestore security rules and the composite indexes that make timeline, search and notification queries resolve rather than scan.
The Technology Behind the Features
One language across the surfaces that matter, and a managed backend that removes a class of infrastructure work from a small team.
Firestore removes the operational burden a small team cannot carry at launch, real-time listeners make feeds and messaging cheap to build correctly, and a managed authentication layer means the riskiest code on the platform is not code you wrote.
Boundaries we state in writing for your build
Named here rather than discovered after the invoice.
What does not arrive is an audience
- Software cannot supply the thing a social network actually runs on, and any vendor implying otherwise is selling you something they do not have. What arrives is a working network with the commercial surfaces attached. Who shows up on it is the part you bring, and it is the slow part.
No media transcoding pipeline
- Video and audio upload and play, but a transcoding pipeline producing multiple renditions and adaptive bitrates is not part of an initial scope. On a platform where members post video freely this is a real cost line and a real piece of engineering, and it is quoted rather than assumed.
One payment rail is referenced
- The build references a Stripe setup. Additional payment rails, regional processors and the merchant relationships behind any of them are integration work on your accounts, and they are scoped and quoted before anything starts.
What is built is real
- 64 API handlers under one versioned surface, 68 web pages, 190 components, 28 mobile screens, a fifteen page operator console on a separate authentication path, twelve Cloud Functions, Firestore rules and composite indexes, ownership checks on every mutation, and an audit entry on every privileged action.
- Clone is the industry term for a platform built to work like a known product. It describes the functional target rather than the origin of the code: this is an original implementation on Next.js, Flutter and Firebase, and it is not affiliated with, sponsored by or endorsed by Twitter or X.
More pages on this build
Five pages describing this proposed build. You are on Features.
The whole network, not just the feed
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Twitter .
Twitter Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Twitter, and how clients search for it.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com