From a session to a subscription
An individual play session earns almost nothing on its own. What compounds is the relationship: a player who comes back every day for eight weeks to chase a reward track. That is the job of the season pass and its cousin, the VIP tier. They convert a one-time distraction into a recurring revenue line — and for mini-games, they have become standard equipment.
The market is already enormous
The global battle-pass market reached about $18.7 billion in 2025, up 31.2% year over year, with 890 million paying users. Mobile alone contributes over 67% of that revenue, and conversion rates are climbing from 22.4% toward 26.1%. The model is no longer a Western console trick; it is the default recurring layer in mobile, and especially in hybrid-casual: by mid-2025, nearly all top hybrid-casual games shipped a season pass.
| Signal | Value |
|---|---|
| 2025 battle-pass market | ~$18.7B (+31.2%) |
| Paying users | 890M |
| Mobile share of revenue | 67%+ |
| Conversion rate trend | 22.4% → 26.1% |
| Top hybrid-casual with a pass | nearly all, mid-2025 |
Why it fits mini-games so well
Mini-games live inside host apps where players already return daily. A season pass rides that habit: a four-to-six-week reward track gives a reason to log in, complete tasks, and stay. The effects show up in the metrics that matter. Publishers like Activision report battle-pass adoption around 42% of active players, lifting ARPPU by roughly 28% season over season, and case studies across Clash, Brawl Stars, and PUBG Mobile show Day-30 retention lifts of 5–10 percentage points after a pass launches.
For emerging markets the tailwind is even stronger: battle-pass user growth hit 41% in Southeast Asia and 37% in Latin America in 2025 — the fastest-rising regions, and exactly where super-app distribution concentrates.
One runtime, one pass system
The friction that stops most studios from adding a pass is building the entitlement, reward-delivery, and entitlement-expiry plumbing per store and per host. A shared runtime centralizes that: the game defines tiers and rewards as config, and the runtime handles unlock, expiry, and cross-host consistency. A VIP tier bought in one host is honored in the next. The developer designs the track; the runtime enforces it everywhere.
What this means for your roadmap
If you build mini-games, a season pass is the highest-leverage monetization you can add after the core loop works — far cheaper than chasing new installs. If you run a host app, offering pass and VIP infrastructure through the runtime lets every title in your catalog sell a recurring product without each team rebuilding the machinery.
Cross Mini App supplies the entitlement and delivery layer once, so a season pass becomes a configuration step, not a per-host engineering project.
