Mini-Game
Super-App
Catalog
Platform
Runtime
Distribution

The Catalog Is the Channel

A deep Q&A on super-app open catalogs — why the host app, not the store, is becoming the distributor

C

Cross Mini App Team

October 31, 2026 · 2 min read

The Catalog Is the Channel

The Catalog Is the Channel

For twenty years the app store was the only door. Now a handful of super-apps — messaging, payments, ride-hailing — are opening their own catalogs of mini-games, and the door is moving. The host app is becoming the distributor, and the catalog is the channel.

Q: Why would a host app want to run an open catalog of mini-games?

Because games are the stickiest content ever built and the host already has the users and the payment rail. A ride-hailing app with a games catalog turns dead waiting time into engaged time, and every session in a game is a session not spent in a competitor's app. The catalog is not a feature; it is a reason to open the app when there is no ride to book. The math is retention, not revenue per se.

Q: What is the runtime problem this creates, and why is one runtime the answer?

Hundreds of games from dozens of studios cannot each ship their own native binary into a host app. That is a security and review nightmare. A single universal runtime — one sandboxed engine that loads any catalog title — means the host approves the runtime once and the catalog grows without per-game review. One runtime is what makes an open catalog open. Without it, the catalog is a walled garden with a very slow door.

Q: For a game studio, is publishing into a catalog better than the app store?

Different, not better. The catalog gives you instant distribution, a built-in payment layer, and zero install friction — but you trade away the direct relationship with the player and most of the pricing control. You are a title in someone's shelf. The studios that win treat the catalog as a top-of-funnel: get the massive cheap reach, then pull the serious players to your own property. The catalog is the mouth of the funnel, not the whole pipe.

Q: What are the real risks of betting on a super-app catalog?

Platform dependency, pure and simple. The host sets the revenue share, the policy, and the discovery ranking, and can deprioritize or delist you overnight. You are building on rented land with a very nice landlord. The mitigation is the same as every distribution channel before it: be where the players are, but own the relationship somewhere you control. A catalog is a channel. It is never the business.

What the host getsWhat the studio gives up
Stickier sessionsDirect player relationship
A reason to openPricing control
Payment rail, readyDiscovery to the host
Cheap catalog supplyOvernight delist risk

The store was never the only door. The catalog just made that obvious — and the studios that treat it as one channel, not the only one, will outlast the hype.

Sources

Related Posts

Schema markup is the invoice machines pay attention to

FAQ, HowTo and Organization markup make a directory legible to machines, but a controlled test shows the gap between being readable and being cited. An honest look at what schema can and cannot do.

Mini Program
Structured Data
AI Citations
November 18, 2026·1 min read
You can't measure what doesn't click

AI discovery happens inside answers that never produce a visit. A practical case for directional metrics like Share of AI Voice, and an honest account of how far attribution can actually reach.

Mini Program
AI discovery
measurement
November 18, 2026·1 min read
AI sends fewer clicks and closes more of them

AI referrals still account for a sliver of site traffic, yet the visits that arrive linger longer and convert at rates organic search rarely matches. This article separates the durable signal from the hype and makes the case for a dedicated catalog entry.

Mini Program
AI traffic
referral marketing
November 18, 2026·1 min read