An experience that adapts — inside the boundaries you design.
AI never rewrites your app or game. Instead, you publish templates — slots with strict schemas, rendered by your own components and game adapters — and Experience Evolution generates, validates, simulates and versions content for them.
Six steps between an idea and your users
You define a slot and a JSON Schema — the only shape content may take.
AI (local by default) or procedural generation drafts variants.
Schema check plus a safety & dark-pattern lint.
Offline player-model simulation for difficulty and missions.
A developer approves; roll out to a percentage of users.
Restore the previous approved version in one click.
Adaptive journeys
Adaptive onboarding
Landing & UI variants
Feature discovery
Contextual content
Living gameplay
Missions & quests
Adaptive difficulty
Procedural levels
Progression & story
Unity today, more engines next
The Unity SDK ships with example adapters for difficulty and daily missions. Unreal and Godot adapters are on the roadmap with a published interface specification.
- Content arrives through the same config call as parameters
- Your components render it — unknown fields are rejected by schema
- Version history for every slot; previous versions restorable
const hero = aop.getExperience<{ headline: string; cta_label: string }>("home.hero");
if (hero) {
render(<Hero headline={hero.content.headline} cta={hero.content.cta_label} />);
} else {
render(<DefaultHero />); // always keep a default
}Generated and hand-written variants are checked for fake scarcity, urgency pressure, confirm-shaming, unsubstantiated claims, external links and personal data. For child or mixed audiences these are hard errors, not warnings.
- • Simulations use a synthetic player model — directional only, confirm with a live test.
- • Image and audio generation are not included yet.
- • A visual template editor is on the roadmap; templates are JSON Schema today.