ShortMax Clone Features: Retention Paid in Inventory
The hardest number in short drama is the cost of a returning viewer. This build treats that as a product problem rather than a media-buying one: the check-in ladder, the referral loop and the campaign desk are shipped modules, and every coin earned, spent, referred or checked in writes a typed ledger row. That is what lets the console report an economy rather than a balance. Here is what ships, grouped by who touches it.
Request a Live Demo →See PricingFeature 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.
The Operator
Permission modules across four actions with staff accounts bound to a named role, and a server-enforced view-only demo operator so a prospect or a new hire can be shown the console without being able to change anything in it.
Five login types and five locales with right-to-left layout for Hebrew and Arabic ship alongside, because a growth-led launch usually means several markets rather than one.
ShortMax vs Miracuves Clone vs Building From Scratch
What each route gives you on the parts that decide whether returning is cheaper than acquiring.
| What decides it | Miracuves ShortMax Clone | Building from scratch |
|---|---|---|
| Time to a working loop | Six working days | A multi-year programme with a senior team |
| Retention mechanics | Check-in ladder, streaks and tasks as shipped modules | The part deferred until acquisition cost becomes painful |
| Referral | Operator-set reward, credited on signup | Usually a share link with no attribution behind it |
| Coin accounting | Seven typed ledger codes on every movement | A balance field, which cannot explain how it got there |
| Reaching your own users | Campaign desk with an in-app inbox, no external service | An email tool and a push provider, both external |
| Analytics | Coin economy analytics tied to the ledger codes | Counts, with no view of what a coin cost to issue |
| Markets | Five locales with RTL, five login types | One market, rebuilt for the second |
| Source code | Full source across web, console and Flutter, yours | Yours, at the cost of building all of it |
ShortMax itself is the reference for what this category looks like; it is not a product you can buy or self-host. The comparison that matters commercially is the second column against the third.
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.
| Module | Why it is in the base build |
|---|---|
| Seven typed ledger codes | A balance field cannot say whether a coin was bought, earned, referred or granted, and that distinction is the difference between a report and a guess. |
| Seven day check-in ladder | Habit forms across days, not sessions. A ladder with a streak is the cheapest retention mechanism available because it pays in inventory. |
| Daily cap on reward tasks | Without a cap the reward economy is farmed within a week and the coin loses whatever value it had. |
| Referral credited on signup | A reward paid later is a reward nobody trusts. Crediting the referrer immediately is what makes the loop actually run. |
| Social follow bonuses | Owned audience on other platforms is free reach. Paying a few coins for a follow is the cheapest channel a new operator has. |
| Campaign desk with inbox | Reaching your own users should not depend on a third-party service being configured and paid for. |
| Five login types | A growth-led launch dies at the sign-up step. More routes in is the least glamorous conversion work and the most reliable. |
| Country filter on analytics | A multi-market launch needs to know which market is working, not just that the total is rising. |
| View-only demo operator | Showing the console to a prospect or a new hire without risking a change is a small thing that removes a real fear. |
The catalog, the vertical player, coin packs and VIP windows all ship as well; this page concentrates on the growth layer because that is what this build is organised around.
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.
What Is Not Included in the Base Package
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.
Every external provider is your own account. Payment gateways, AdMob, Firebase push, Resend mail and S3 or DigitalOcean storage all run on credentials you hold.
The controls that are built are real: permission modules across four actions, staff accounts bound to a named role, and a server-enforced view-only demo operator.
See how Miracuves compares to agencies and freelancers
The deployment process, a modelled reference deployment for a referral-led launch, and what to check on the ledger and the reward caps before you hire anyone - on the Development Company page.
Frequently Asked Questions
Why does the ledger need seven codes?
What stops the reward economy being farmed?
Do campaigns need a push provider?
Can I track which ad campaign brought a viewer?
Why do rewarded ads only work properly on mobile?
How does referral actually credit the referrer?
See a coin earned, spent and reported, live
Ask for the demo and we will claim a check-in, watch a reward task credit the wallet, follow the referral link, then schedule a campaign and watch the inbox row appear.
Explore the ShortMax Clone
Ready to make returning cheaper than acquiring?
Deploy in six working days with the rewards ladder, the referral loop, the campaign desk and the typed coin ledger included, your reward amounts and caps configured with you, and the full source on infrastructure you own.
Talk to Us →Miracuves is an independent software development company. 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.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the ShortMax website or applications.
ShortMax and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
