Xyplor
Long-form projects

A one-shot game was never the goal.The project is the point.

Most AI tools hand a kid a game in sixty seconds and then nothing to come back to. Builds let a child take one ambitious project from idea to a playtested, portfolio-ready game — iterated over weeks, with milestones, version history, and full parent visibility.

Start free How we keep it safe

The one-shot trap

When a tool has no concept of yesterday's thing, every session is a fresh blank box. The child practices asking and never practices steering — and steering is the skill that actually matters with AI: look at what came back, notice it is not right, be specific about why, ask again, repeat.

A child who has made forty small games has a folder of demos. A child who has made one game forty times has shipped something — and has practiced the entire loop the first one skipped. That loop is the whole game. Builds exist to make it possible.

What a real project needs

Most "AI for kids" products have none of these. A long-form project needs all four — and it is a fair checklist for any tool, not just ours.

Memory across sessions

An optional backstory — a short world bible — plus the project's recent history is carried into every session, so the child iterates one coherent thing instead of re-explaining it each visit.

Milestones

The child names what is next — add a second level, make the boss harder, add a title screen — and tracks it as todo, doing, done. Planning gets practiced; a stuck kid has a written next move instead of a blank-box panic.

Version history you can rewind

Every version is kept and any one can be restored. Reversible mistakes make a child brave enough to take real swings — which is the whole point of iterating.

An arc you can show

The portfolio artifact is not the final game — it is the sequence. A public arc page shows every version with the child's own change notes, the way an artist shows process. Private until the child chooses to share it.

Builds, at a glance

  • On the free plan. Making and iterating your own Builds is not a paywalled upsell. Co-creating a Build with a friend is a Pro or Max feature.
  • One coherent surface. The live, playable game alongside milestones, a rewindable version history, and suggested next steps for when a kid is unsure what to improve.
  • It streams. The child watches the game come together, not a spinner.
  • Quick ideas can grow. Any one-shot creation can become version one of a Build without losing anything.
  • Private by default. Publishing the public arc page is a deliberate, separate choice.
  • Parent-visible. Active Builds show on the parent dashboard, alongside the full logged AI conversation history.

We teach AI direction, not programming. This is creative screen time — a child directing a tool — not the only screen time a kid should have.

Questions parents ask

What is a Build?▾
A Build is a long-form project a child returns to over weeks instead of a one-shot creation. The child gives it a title, a one-line pitch, and an optional backstory, then iterates the same game across many short sessions — adding levels, fixing what is not fun, making it deeper each time.
How is this different from other AI tools for kids?▾
Most AI tools produce a game in about 60 seconds and then forget it — the next visit starts from a blank box. A Build persists: the AI carries the project's context from session to session, so the child practices steering and improving one thing over time rather than producing a daily pile of disposable demos.
Does my child need to know how to code?▾
No. Xyplor never claims to teach programming. Children describe what they want in plain English and judge what comes back. The skill being practiced is AI direction — holding an intent, evaluating the result, and iterating deliberately — not syntax.
Is Builds a paid feature?▾
No. Making and iterating your own Builds is available on the free Xyplor plan. Inviting a friend to co-create a Build together is a Pro or Max feature, but building your own projects is not paywalled.
Can other people see my child's project?▾
A Build is private by default. A child can choose to publish its public arc page — the whole version timeline with their own change notes — but that is a deliberate, separate step, never on by default.
What can a parent see?▾
Parents see each kid's active Builds on their dashboard — how many versions in, milestones done, when it was last worked on — alongside the full, logged AI conversation history that is visible across all of Xyplor. Supervision is informed, not a black box.
What ages is this for?▾
Xyplor is built for kids ages 6 to 17. Younger kids enjoy a game that exists; older kids want the deep version that takes many iterations — long-form Builds are designed for exactly that progression.
Can a one-shot creation become a Build?▾
Yes. A game a child made in a single session can be turned into version one of a Build without losing anything, so a quick idea can grow into a long-form project.

Xyplor was built by an engineer and parent whose two kids, ages 8 and 11, are its daily testers — and Builds exist because the older one kept asking for the deep version of his game and a one-shot tool could not give it to him. There is a deeper read on why a one-shot game isn't enough, and a homeschool-shaped on-ramp at xyplor.com/homeschool.

Start a project free