Jest and RCS: is messaging-native game distribution worth a test?

Direct answer — should your studio test RCS messaging as a game distribution channel in 2026? Only if you already have a mobile web build and monetise through in-app purchase rather than rewarded video. Jest, the first venture-funded entrant on this rail, is live in the United States only and publishes a Q3 2026 roadmap of fourteen further markets; its published economics give developers 90% of net in-app purchase revenue, and its documentation caps re-engagement at one notification per user per day across every game on the platform. For a web-ready IAP title that is a cheap experiment. For an ad-monetised one it is a non-starter, because Jest’s documentation states it does not currently support rewarded ads.

Jest came out of stealth in February 2026 with “$7 million in seed funding led by Innovation Endeavors”, per TechCrunch, and a pitch aimed at the store duopoly: distribute games through the phone’s native messaging inbox — SMS and RCS — instead of an app store. The games trade press has barely touched it since.

That deserves a look, and a boundary. We have already published the playbook for instant games inside Telegram, TikTok and Messenger: platform-embedded mini-games on a chat platform’s own surface, under that platform’s SDK and rules. Jest is a different animal. It routes through carrier messaging rails — the SMS and RCS pipes your bank uses for one-time codes — and the game runs in the mobile browser. Different gatekeeper, different compliance regime, different economics.

What Jest actually is, and what it is not

Start with the mechanic, because the marketing obscures it. Jest’s own site says “Apps run in the browser. Messaging drives distribution and engagement,” and its documentation is blunter: “Jest is a marketplace for messaging apps. Messaging apps are web apps that use texting protocols (SMS and RCS).”

Read that twice. The game is a mobile web build. Messaging is the acquisition and re-engagement rail, not the runtime. Jest’s technical requirements state that “all published games must be playable in a web browser” and that a title “must be optimized for mobile, including support for touch input, a responsive layout that adapts to different screen sizes”. Its SDK covers Unity (WebGL), Godot, HTML5 and other engines.

That collapses the integration question. If you already ship a mobile web build — for a portal, a web shop, an instant-games surface — testing Jest costs an SDK integration and a listing, not a port. If you do not, it costs a web build, which is a project rather than an experiment. Sequencing a channel against what your pipeline already produces is the point of our multi-channel distribution framework, and the modelling our distribution practice runs before anyone signs.

What Jest is not: a store you install, a chat-platform mini-game, or a messaging client. It is a mobile web catalogue with a texting layer on the retention loop.

What is verifiable, and what is only claimed

Jest is six months old and the most detailed account of it is its own. The revenue terms, fund structure, platform rules and geographic footprint are published first-party — commitments you can hold a partner to. Everything else needs a label.

Verifiable but self-reported. The performance numbers come from Jest. Its developer page attributes them to “a 4-month test (Oct ‘25-Jan ‘26) with US mobile users” and reports “3-4x Higher Retention” measured as D7 retention, and “35–60% Cheaper User Acquisition” measured as mobile app cost per install against messaging app cost per texting subscriber, across “1M+ app opens and 300K+ messages sent”. That compares Jest’s messaging version of a title against the same studio’s mobile app version, over four months, in the United States, on a self-selected beta cohort — no independent measurement, no published sample of titles. A reason to run your own test, not a substitute for one.

Claimed, with no source. The launch press release states that “RCS adoption accelerates past 3.8 billion monthly active users” and attaches no attribution to it; neither Jest’s site nor its documentation publishes any reach figure at all. The only first-party RCS volume figure we could verify is Google’s: in May 2025 Google said “there are more than a billion RCS messages sent every day (based on an average of the last 28 days)” — a message count, not a user count, scoped to the United States. Treat any global RCS user number in this category as unverified.

Named partners. The release names “Pocket Gems (Episode), Global Worldwide (Kingdom Maker), HayHay (Puppy Mansion), Nowwa (Super Snappy Go), HG Point (Piece of Cake), and Dominion Games (Opps)” — real studios with real titles, a meaningful signal for a company this young, but not a revenue disclosure.

One thing has already moved. At launch the fund was announced as “$1M for flagship, $200K for promising, and $40K for exploratory titles”. Six months on, Jest’s own fund page — now the Jest Apps Fund, not the Jest Games Fund — lists different tiers and discloses their composition: Flagship is “$900K UA budget” plus “$100K for 40 onboardings”; Scale is “$75K UA budget” plus “$25K for 10 onboardings”; Explore is “$10K/app”. That is not a cash advance. It is media spend on Jest’s own platform plus integration services, and Jest states it takes “an increased platform revenue share” in return. Negotiate against the live page.

The economics, and the three rules that decide the outcome

The headline rate is good; the rules underneath it decide the outcome.

The split. Jest’s platform economics page states that “Jest charges 10% of net in-app purchase revenue” and that “The remaining 90% of net revenue goes to developers.” Read “net” carefully: Jest defines it as the revenue “that reaches our bank account from in-app purchases, after deducting payment processing fees, taxes (like VAT), refunds, chargebacks, and fraud”. So 90% of net, not of gross — still a strong rate against any mobile storefront, and Jest says the same 10% covers messaging, hosting and fraud prevention. Purchases are priced in USD; payouts are “processed monthly”.

Rule one: no rewarded ads. Jest’s gameplay requirements state that “Jest does not currently support rewarded ads. Games must not include mechanics that rely on rewarded ads for progression, rewards, or other gameplay elements.” Across much of the web-native and casual catalogue, rewarded video is the workhorse and IAP the minority earner — the pattern running through the published terms of every HTML5 monetisation channel we mapped. If your economics rest on rewarded video, 90% of an IAP line you barely have is not a business. This rule disqualifies more candidate titles than anything else here.

Rule two: you do not own the message. Jest’s notification documentation states that “At most one notification per user per day across all games on the platform may also be delivered to the user’s messaging inbox”, and that “The platform selects which notification to deliver and when”. Your re-engagement channel is shared, capped and arbitrated by the platform. Carrier compliance leaks into the creative too: bodies should stay under 100 characters, “texting has mandated quiet hours”, and SHAFT content — sex, hate, alcohol, firearms, tobacco, gambling and drugs — “is not allowed and will be blocked”.

Rule three: acquisition is shared too. Where one app acquires a player and another monetises them, Jest’s economics page splits it 70% to the monetising app, 20% to the acquiring app and 10% to Jest, with the acquiring app earning its share “for up to 12 months or until the user becomes inactive, whichever comes first”. A useful cross-promotion primitive if you run a portfolio.

How far does the channel actually reach?

Reach is where the pitch and the documentation diverge most. Jest’s availability page says the platform is “live in the United States” and names the next wave for Q3 2026 — France, Germany, Spain, the United Kingdom, Brazil, the Netherlands, Austria, Italy, Norway, Portugal, Singapore, South Africa, Sweden and Canada. Fourteen markets, none shipped yet.

The underlying constraint is that RCS is a carrier service, not an internet service. Google’s own support documentation tells users that if “RCS chats are disabled by your carrier” appears, they should “contact your carrier”. Apple added RCS to Messages in iOS 18, announced in June 2024 — “the Messages app now supports RCS for richer media and more reliable group messaging compared to SMS and MMS” — the change that made the rail cross-platform. But availability still resolves operator by operator. That is why Jest launches country by country, and why a single worldwide RCS reach number would mislead even if a credible party published one. Jest’s own rollout had the same shape: it announced RCS on 15 November 2025 and said it would arrive “gradually”.

The practical read: today this is a United States channel. If your revenue is concentrated in APAC or LATAM, it is a Q4 2026 conversation at the earliest.

Should you test it, and what would you measure?

Test it if four things are true at once: you have a mobile web build or can produce one cheaply; your monetisation is IAP-led rather than rewarded-video-led; the United States is a meaningful market for the title; and the game has an appointment or daily-reward loop that a once-a-day message can serve. Jest’s gameplay requirements are explicit that titles should include “appointment mechanics, time-limited events, daily rewards, or other incentives tied to the player’s in-game state”. The channel is built for that shape and underperforms for anything else.

Do not test it if your title needs rewarded video, needs a large download to look right, or if you would have to fund a web build to find out.

If you run it, measure three things against your own baseline rather than Jest’s: D7 retention on the messaging cohort versus your app cohort for the same title; cost per registered texting subscriber against your blended CPI; and net revenue per registered user after the 10%. The channel earns an experiment for the reason we argue for distribution beyond paid UA — an install you did not buy at auction is worth more than a few points shaved off a commission. But that only pays if the retention holds, and the only retention data that exists today is the vendor’s.

Set a kill criterion before you start: one quarter, one title, one hypothesis. That is the right size of bet for a channel with real funding, real partners, and no independent evidence yet.

FAQ

Is Jest available outside the United States?

Not yet. Jest’s availability documentation says the platform is “live in the United States” and lists fourteen further markets for Q3 2026: France, Germany, Spain, the United Kingdom, Brazil, the Netherlands, Austria, Italy, Norway, Portugal, Singapore, South Africa, Sweden and Canada. The pace is set by RCS itself, a carrier service enabled operator by operator rather than a global internet service.

Can I run rewarded video ads on a Jest game?

No. Jest’s gameplay requirements state that “Jest does not currently support rewarded ads” and that games “must not include mechanics that rely on rewarded ads for progression, rewards, or other gameplay elements”. Monetisation runs through Jest’s own in-app purchase APIs, priced in USD. For titles whose economics depend on rewarded video, that rules the channel out however attractive the 90/10 split looks.

How is Jest different from Telegram, TikTok or Messenger instant games?

The gatekeeper is different. Telegram, TikTok and Messenger host mini-games on their own surface, under their own SDK and rules, reaching that platform’s user base. Jest routes through carrier messaging rails — SMS and RCS — and the game runs in the mobile browser rather than inside a chat client. That changes who can block you, which compliance rules apply (quiet hours, SHAFT content restrictions), and how the channel expands geographically, since carrier support is granted market by market.

---

If you want a candid read on whether a messaging-native channel belongs in your 2027 plan, and how to sequence it against the stores, OEM channels and web-native surfaces you already run, we would be glad to talk. Early-stage teams can see how we share the operational load in our founding developer programme.