ShortMax Clone Features: Retention Paid in Inventory
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 growth loop is designed to land on the store build, where the rewards, the referral and the ad unlock all actually run.
The Returning Viewer
- A seven day check-in ladder with a streak, ad reward tasks under a daily cap, follow bonuses for Instagram, Facebook and TikTok, an email bonus and a login bonus. Each one pays out in coins the operator issues rather than cash, which means return visits are bought with inventory at a cost you set.
The Referrer
- A referral loop with an operator-set reward amount, crediting the referrer on signup so an existing viewer becomes an acquisition channel. Referral is the one line that reduces a cost rather than adding revenue, and it compounds as the base grows.
The Campaign Operator
- Campaign templates, audience selection, scheduling and cancellation, and campaign statistics, with an in-app inbox row written for every targeted user. The campaign desk and the inbox work without any external service, which matters because it means reach does not depend on a push provider being configured.
The Economy Analyst
- Coin economy analytics tied to the seven ledger codes, alongside overview counts and charts, user analytics with a country filter, paid revenue monitoring, series revenue breakdown and top revenue episodes. The question this answers is not what the balance is but what it cost to create.
The Mobile Viewer
- The Flutter store build with five tabs: episode-wise reels, rewards quests, referral, coin and AdMob ad unlock, and wallet histories, in the same five locales. This is where the growth loop lands, because the live rewarded ad path exists on the store build rather than on the web.
How It Works, End to End
One viewer, traced from a referral link through to a coin economy report, with every movement carrying its own ledger code.
They arrive through somebody already here
- A referral loop with an operator-set reward amount credits the referrer on signup. Five login types mean the sign-up step is not the place the funnel breaks, which matters more in a growth-led launch than almost anything else on this page.
The first coins arrive without a purchase
- A login bonus, an email bonus and follow bonuses for Instagram, Facebook and TikTok give a new viewer a balance before they have spent anything. Those coins cost inventory rather than cash, which is the whole economic argument of this build.
Every movement writes a typed row
- Earned, spent, referred, checked in: each coin movement writes a ledger row carrying one of seven codes. That typing is what turns a wallet into an economy you can report on, because the console can then say what a coin cost to create rather than only what the balance is.
The ladder gives them a reason to come back
- A seven day check-in ladder with a streak, plus ad reward tasks under a daily cap. The cap is the control that stops the reward economy from being farmed, and it is an operator setting rather than a constant, so it can be tightened once you see behaviour.
Coins open episodes
- The earned balance meets the locked episode. Coin, VIP entitlement or an AdMob rewarded ad on the store build can each open it. A viewer who has never spent cash still reaches the content, and still generates revenue through the ad path.
The operator reaches them without a middleman
- Campaign templates, audience selection, scheduling and cancellation, with an in-app inbox row written for every targeted user. The campaign desk and the inbox work without any external service; device push additionally needs your own Firebase project configured.
The economy reports on itself
- Coin economy analytics tied to the ledger codes, alongside paid revenue monitoring, user analytics with a country filter, series revenue breakdown and top revenue episodes. The question a growth-led operator asks is which title returned the spend, and this is where that is answered.
Every Feature Earns Its Place
Each module below exists because a growth-led platform 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 typed ledger is the number that matters
- Coins issued as rewards cost inventory. Coins sold cost nothing but the gateway fee. Those are completely different economics arriving in the same wallet, and a platform that stores a single balance cannot tell them apart afterwards. Seven typed codes on every movement is what makes it possible to say what your retention actually cost, which is the only question a growth-led operator genuinely needs answered.
- The stack is Express and MongoDB with a Next.js console and a Flutter build, on standard infrastructure you own and can hire against.
Boundaries we state in writing for your build
Named here rather than discovered after the invoice.
Stated limitations and what needs your account
- Passwords use reversible encryption. Not one-way hashing. On a platform holding wallet balances this is the item we would schedule first, and it is straightforward scoped work that costs less before a live user base than after.
- There is no attribution, deep linking, UTM tracking, cohort analysis or A/B testing module. The analytics are operational counts and revenue breakdowns. For a growth-led operator that is a real gap worth reading twice: you can see what the economy did, but not which external channel produced it.
- Web ad unlock is a simulated timed preview rather than a live ad network. AdMob on the Flutter store build is the live path, so rewarded ad revenue should be modelled against the store build rather than the web.
- Device push needs your own Firebase project. The campaign desk and the in-app inbox work without any external service, so a campaign still reaches every targeted user in the app, but it will not arrive as a device notification until Firebase is configured.
Ready to make returning cheaper than acquiring?
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by ShortMax.
ShortMax Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to ShortMax, 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 ShortMax.
ShortMax Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to ShortMax, 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.