MoboReels Clone Features: The Catalog Is the Product Surface
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
The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.
Feature Set by Role
Three clients on one Express and MongoDB API. The same catalog feeds the consumer web app, the Flutter store build and the console, so a title reordered on Tuesday is numbered the same way everywhere on Tuesday.
The Viewer
- A surface driven entirely by the catalog: banner rails, trending, new releases, coming soon and For You trailers, with title and plot search behind a genre filter. The player is vertical and episode-wise with subtitles, and what a viewer can open depends on the lock state carried by each episode record rather than on a separate entitlement system.
The Catalog Editor
- Film category, film list and episode list as three working modules. A title is typed as a movie or a web series, carries poster and banner artwork, and has trending, coming soon and active toggles. Publishing is a console task rather than a migration script somebody runs against the database.
The Episode Operator
- Episodes carry a number, a coin price and a lock state each. Drag and drop reorder renumbers the sequence and reapplies locks in the same action, which is the one operation a published short-drama library needs most and the one most platforms leave to a manual clean-up.
The Localisation Lead
- A subtitle upload dialogue per episode, five locales with right-to-left layout for Hebrew and Arabic, and app language JSON editable from the console. A library sold into more than one market is a translation problem before it is a distribution problem, and both live in the console here.
The Revenue Analyst
- Overview counts and charts, series and episode level performance, revenue by series, users and wallets, plans and orders, and reports. Series revenue breakdown and top revenue episodes are what a rights holder asks to see, and they are assembled from operational data rather than by exporting collections.
The Operator
- A 24-module permission system with staff accounts bound to named roles, storage switchable across local, S3 and DigitalOcean Spaces, and magic-byte inspection on every upload. The console governs the library rather than merely reporting on it.
How It Works, End to End
One title, traced from an empty category through to a rights holder statement, with numbering and locks holding throughout.
The category and the title are created
- A film category is created, then a title inside it typed as a movie or a web series. Poster and banner artwork attach to the title itself, along with trending, coming soon and active toggles. From this point the title is an operator record rather than a row somebody has to remember to update.
The title is reordered without breaking
- Episodes reorder by drag and drop, and the platform renumbers the sequence and reapplies the locks in the same action. This is the operation that separates a working library from a published mistake, because a reorder that leaves numbering stale strands exactly the viewers who already paid.
Rails are composed, not generated
- Banner rails, trending, new releases, coming soon and For You trailers are operator-composed rather than produced by a recommendation engine. That is a deliberate limitation and a deliberate control: what a viewer sees first is an editorial decision, which is what a catalog-led operator actually wants.
The viewer opens an episode
- The vertical player runs episode-wise with subtitles. Unlocking draws on the coin balance, a VIP entitlement window, or a rewarded ad on the store build. Which tender is available is an operator setting rather than a property of the viewer's account.
The library reports on itself
- Overview counts and charts, series and episode level performance, revenue by series, top revenue episodes, users and wallets, plans and orders. A rights holder asking which titles earned gets an answer from operational data rather than a spreadsheet assembled from exports.
Every Feature Earns Its Place
Each module below exists because a catalog-led library stops working without it, not because a competitor lists it.
The Technology Behind the Features
What the platform is actually built on, and what that means for the team who inherits it.
Why the catalog model is the number that matters
- A vertical player is a weekend. What takes months is a library that can be edited after publication without breaking: numbering that follows a reorder, locks that follow the numbering, artwork bound to the title rather than the release, subtitles that cannot drift from their episode, and pricing granular enough to be a commercial lever rather than a single field. Thirty-three models is not a boast, it is what modelling a library properly costs.
- The admin surface being two-thirds of the API is the clearest signal of what this build is for: operating a library rather than playing one.
Boundaries we state in writing for your build
Named here rather than discovered after the invoice.
Stated limitations and deployment choices
- Passwords use reversible encryption. This is stated plainly because it matters: it is not one-way hashing, and for a platform holding customer accounts it is work we would recommend scheduling before launch rather than after. Ask us about it directly on the first call.
- There is no season container. A multi-season library is modelled as separate titles. If your catalog is season-heavy that shapes how you structure it, and it is better known now than after the library is loaded.
- There is no recommendation engine. Rails are operator-composed. For a catalog-led operator that is often the point, because what a viewer sees first stays an editorial decision, but it is a limitation rather than a feature and we name it as one.
- Web ad unlock is a simulated timed preview, not a live ad network. AdMob on the Flutter store build is the live path. Any revenue model that leans on rewarded ads should assume the store build carries it.
Ready to run a short-drama library you actually own?
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by MoboReels.
MoboReels Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to MoboReels, and how clients search for it.
More pages on this build
Overview
The full proposal on one page.
Features
Every proposed capability grouped by who touches it.
You are hereBusiness model
How a platform in this category earns, and which lever to switch on first.
Cost
What actually moves the budget, and how a scope-first written quote is put together.
Company
Agency versus freelancer versus Omnistu, plus the checks to run before hiring anyone.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by MoboReels.
MoboReels Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to MoboReels, and how clients search for it.
Discuss your scope by message
Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
