External Games
External games are ResultFly UI components rendered from third-party web apps. They live in page nodes alongside native controls but are hosted and maintained by external teams. This section outlines the platform responsibilities, the wrapper component, and the integration contract.
Why externalize games
- Allow brands to ship bespoke mechanics while using ResultFly flows, targeting, and analytics.
- Keep ResultFly releases decoupled from each game’s lifecycle; the component merely embeds a remote bundle.
- Maintain a governed interface so that external code cannot break the studio experience or corrupt session data.
What is covered here
- External Game Component — how a
type=pagecomponent references the external iframe, what settings editors configure, and how the runtime treats the block. - Contract & SDK — lifecycle, messaging schema, validation rules, and the helper SDK contract that developers follow when building their game.
With these artifacts in place we can document the expected behavior today and later publish the actual SDK/tooling without changing the contract.
Last updated on