Update your in-game store without an app release

There is exactly one moment in your monthly LiveOps cycle that's truly broken, and you've stopped noticing because everyone has the same problem.

It's the moment you have a great idea for a new offer screen. A carousel instead of a single card. A countdown ring around the buy button. A new animation that mimics the one the #1 game in your genre just shipped.

You estimate the engineering work. You schedule a release. You write the spec, hand it off, wait for QA, push to internal builds, push to production, wait three to seven days for store review, ship the app, watch your update adoption curve plateau at 50%, and find out that the new screen has been live for two weeks but only half your players have ever seen it.

Six weeks have passed since the idea. Three of those weeks were store review and player update lag. Of the players who DID update, the ones who matter most — the whales who spend $50+ a month — got the new screen the slowest, because they had session continuity and never relaunched.

That's the most expensive ~30 days in your studio.

What we do differently

We don't bake your offer screen into the app you ship.

The app you ship is a thin shell. It says "when the SDK fires the show-an- offer event, render the current offer screen design." The "current design" is something we send your game over the air. When you change it from your dashboard, every player gets the new one the next time they open your game.

There are two ways to change it:

The 60-second version

You want to recolor everything for Halloween. Cyan accent → ember orange. Border radius → cut-corner instead of round. New backdrop image. The kind of change that, in your old setup, was a designer-week followed by an engineering sprint.

In our dashboard, you change the theme tokens and hit save. Every player on every device sees the new look within 60 seconds. No app update. No store wait. No "please update" prompt that half your players ignore.

The few-minutes version

You want a brand-new layout — a carousel of three offers instead of one card. A skin built around a movie tie-in. A completely different visual treatment for whales versus new players.

In our dashboard, you push a new design. We deliver it directly to every copy of your game already on every device. The next time a player opens the app, they pick up the new screen silently. Their session restores exactly where it was. They never see an "update required" message, because there is no app update.

How your AI agent gets it done for you

If your team doesn't have a developer specialising in UI animation work — and most game studios don't — this is where it gets interesting.

Point your AI agent — Claude, ChatGPT, Cursor, whatever you use — at your existing Unity offer screen. Our tooling reads your prefabs, your animations, your DOTween calls, your sprite atlases. It emits a finished design file plus a configuration of which slots map to which AI signals.

You review it in our preview tool. You push it from the dashboard. Live in minutes.

What this means a year from now

Every game in your genre will be experimenting with new offer-screen patterns constantly. The studios that can ship a new screen the same week the trend appears will win. The studios stuck in app-release cycles will ship three iterations a year while their competitors ship thirty.

We built this so you're the studio that ships thirty.

See how the store-update pipeline actually works →

Talk to us about shipping faster than your competitors →