makie.kidsai.app

Makie turns a kid's spoken or typed idea into a real, playable game by having the child describe what they want, then generating working code that appears as a game in about a minute. It's built for ages 7–15, requires no coding class or setup, and lets kids keep changing the game with single sentences. The catch: creation runs on weekly Make Credits managed by an adult in the household, so it isn't an unlimited free-for-all.

The maker loop: say it, see it, play it

Makie's core loop is deliberately short. According to the site, the sequence is:

1. Describe your game in your own words — a phrase like "a dragon that catches falling stars" is enough.
2. Watch Makie write real code, live — the child sees code being produced, not just a finished result.
3. Change anything with a single sentence — swap the hero, rewrite the rules, replace the whole world.
4. Peek at the real code and learn how it works — curious kids can read what was generated.
5. Publish a play-link in one tap — share with friends and family.

The site states a real, playable game appears in about a minute. That speed matters for young makers: the gap between "I imagined this" and "I'm playing it" stays short enough to hold attention.

What the child actually does

There are two entry points, and the choice affects how much scaffolding the child gets:

From there, the four-step flow is: pick a starter or blank canvas → tell Makie what to make → play, remix, repeat → publish and share.

The "remix everything" idea is the part worth understanding. A child isn't locked into their first description. Changing the hero, the rules, or the entire world is framed as being "one sentence away." That means iteration is the main activity — not one-shot generation.

Why the code is visible, not hidden

Most "describe a game" tools hide the machinery. Makie shows it. Kids can watch code being written live and then read the real code afterward.

This serves two purposes:

• It demystifies how games work. A child who changes a rule and then sees which line changed learns cause and effect.
• It creates a path from playing to understanding. The site frames this as learning by creating, consistent with its sibling app Askie, which the same team built for kids to explore through voice, stories, and art.

If your goal is purely "keep them entertained," the code view is optional. If your goal is "they learn something about how software is made," it's the most valuable part of the product.

Safety and limits parents should know

Makie's safety model is stated directly on the site:

• Filtered by design — every idea passes through kid-safe content filters before anything is built.
• No ads, no strangers — no advertising, no chat with strangers, and the site says no data is sold.
• Healthy limits — weekly Make Credits make costs clear and keep creation intentional.
• One household, every maker — adults manage household access, maker emails, credits, and billing.

Two practical implications:

1. An adult needs to set up and manage the household. This isn't a drop-in tool a child signs up for alone.
2. Make Credits are a real constraint. The site describes them as weekly and adult-managed, which means heavy creation days can hit a ceiling. The exact credit amounts and any pricing tiers aren't specified in the available information — check the Pricing and credits page before assuming a cost structure.

Sharing without accounts

Publishing produces a play-link, and the site states no accounts are needed to play. So a grandparent or a friend can open the link and play the game without signing up. That removes most of the friction that normally kills kid-made projects — the audience can actually reach the thing.

What Makie is not

• It's not a coding curriculum. There are no lessons or levels; the learning is a side effect of making and reading code.
• It's not for kids outside the stated 7–15 range, and it's not designed for unsupervised signup.
• It's not a chat or social platform — the site explicitly rules out stranger chat.

The bottom line

If you want a child to go from a one-sentence idea to a playable, shareable game in about a minute — and to be able to read the code behind it — Makie is built exactly for that. The conditions are: the child is roughly 7–15, an adult sets up the household and manages weekly Make Credits, and you're comfortable with creation being intentionally rate-limited rather than unlimited.

Makie is a game-making tool for kids ages 7–15 where a child describes a game in their own words and Makie turns it into a real, playable game. Safety here isn't a settings menu you have to hunt through — it's built into how the product works. Every idea passes through kid-safe content filters before anything is built, there are no ads and no chat with strangers, and an adult in the household manages access, maker emails, credits, and billing. If you're a parent deciding whether to let your child use it, the sections below cover what's actually enforced and what stays in your hands.

Content filtering happens before anything is built

The key detail is the order of operations: filtering is not a review step after a game exists. According to Makie, every idea passes through kid-safe content filters before anything is built. That means a prompt that doesn't clear the filter never becomes a game in the first place, rather than being caught and removed later.

This matters for how you talk to your kid about it. The maker loop is:

1. Describe your game in your own words
2. Watch Makie write real code, live
3. Change anything with a single sentence
4. Peek at the real code and learn how it works
5. Publish a play-link in one tap

Filtering sits at the front of that loop, so the "describe it" step is the one that's screened. Remixing and editing afterward stay inside a game that already passed.

No ads, no strangers, no data sold

Makie states these as flat commitments rather than defaults you can toggle:

• No advertising
• No chat with strangers
• No data sold — "ever"

For a 7–15 age range, the absence of stranger chat is the piece that changes the risk profile most, because it removes the usual pathway for contact from people outside the household. Combined with no ads, there's also no mechanism pushing your child toward purchases or external links while they're creating.

Weekly Make Credits keep costs visible and creation intentional

Makie uses weekly Make Credits as its cost model. The stated purpose is twofold: making costs clear, and keeping creation intentional — a child can't generate endlessly without limit, and a parent can see what a week of making actually consumes.

Two practical notes:

• Credits are described as weekly, so the natural rhythm is a recurring allowance rather than a one-time purchase.
• Makie publishes a Pricing and credits page, which is where current credit amounts and any paid tiers should be checked — those specifics aren't fixed in the material above, so treat the pricing page as the source of truth before you commit.

If your concern is "will this quietly run up a bill," the credit model is the answer to look at first, and the household billing controls below are the second half of it.

One household, one adult in charge

Makie is built around a household account rather than individual child sign-ups. Adults manage:

This structure is what makes the safety claims enforceable in practice: filtering and no-stranger-chat are platform-level, while access and spend are parent-level. A child can create and publish a play-link without an account of their own, and publishing is one tap — but the household frame is set by the adult.

What "safe by design" does and doesn't cover

Worth being precise, because "safe" gets used loosely:

Covered by Makie's stated design:

• Idea-level content filtering before build
• No ads, no stranger chat, no data sold
• Credit limits that cap runaway creation
• Adult-managed access, emails, credits, billing

Not something the product claims to do for you:

• Judge whether a specific game is appropriate for your specific child
• Replace your involvement in what they're making

The practical move is to use the household controls as intended — set up access yourself, watch the first few credits get spent, and look at what gets published. Makie also provides a Parent guide and FAQ alongside its safety information, which are the right places to check for anything that changes after this writing.

Who this is built for

Makie comes from the same small team behind Askie, an AI learning companion for kids. The framing they use is that Askie is where kids wonder and Makie is where they build — same approach to child safety and the same design philosophy across both. If your family already uses Askie, the safety model and household setup will feel familiar.

For ages 7–15, the combination that matters most is: filtered before build, no strangers, no ads, capped weekly credits, and an adult holding the keys to access and billing. That's the whole safety story, and it's checkable — start at the pricing and credits page and the parent guide before you sign up.

Makie and Askie are made by the same small team, and they split one job between them: Askie is where kids wonder, Makie is where kids build. If your child already uses Askie, Makie is the natural next step — instead of exploring the world through voice, stories, and art, they describe a game and get a real, playable one back. Both apps share the same approach to child safety and the same warm design, so the experience feels continuous rather than like switching to a different product.

The same team, two different jobs

Makie's own site states it plainly: Makie is built by the same small team behind Askie, "the AI learning companion where kids ask anything and explore the world through voice, stories, and art." The stated through-line is "the same obsession with child safety, the same warm design, the same belief that kids learn best by creating."

The division of labor is captured in one line on the site:

Askie is where they wonder. Makie is where they build.

What carries over from Askie to Makie

The shared design philosophy shows up in concrete choices rather than just branding:

• Safety-first filtering. Makie says every idea passes through kid-safe content filters before anything is built. The site also states there are no ads, no chat with strangers, and no data sold.
• Parent-managed access. Adults manage household access, maker emails, credits, and billing — a single household can hold multiple young makers.
• Creation as the learning method. Both apps rest on the same belief that kids learn best by creating, just applied to different materials (conversation and art in Askie, game logic and code in Makie).

What Makie adds that Askie doesn't cover

Makie extends the family into making and sharing:

• Kids describe a game in their own words and watch Makie write real code live.
• They can change anything with a single sentence and peek at the real code to see how it works.
• One tap publishes a play-link for friends and family, and no account is needed to play.
• Weekly Make Credits keep costs visible and creation intentional, per the site's parent-facing section.

Which one fits your child right now

• Choose Askie if your child is in a question-asking, story-and-art phase and you want a companion for exploring.
• Choose Makie if your child wants to make something playable and share it — the site positions it for ages 7–15.
• Use both if you want the full arc: wondering in Askie, then building in Makie, under the same safety model and the same household account setup.

If you want to see the other half of the family, the site points to Askie at kidsai.app.

Makie is a web-based AI game-making platform for kids ages 7–15, where a child describes a game in their own words and Makie turns it into a real, playable game they can keep changing. It's built by the same team behind Askie, an AI learning companion for kids, and it's designed so that parents manage access, credits, and billing for the household. If you're a parent looking for a creative, safety-focused tool for a child in that age range, or you want to understand what your kid would actually do on the site, this covers what Makie does and how it works.

What Makie actually does

The core promise is stated plainly on the site: "Your idea. Your game." A child doesn't need to learn a programming language or sit through a coding class first. They describe what they're imagining, and Makie generates a playable game from that description.

The site gives a concrete example of how little input is needed: "A dragon that catches falling stars" — that's all it takes. According to the site, a real, playable game appears in about a minute.

From there, the game isn't frozen. Kids can remix it — change the hero, the rules, the whole world — and each change is "one sentence away." Curious kids can also open up and read the real code behind their game, so the tool doubles as a gentle introduction to how code works.

The maker loop, step by step

Makie describes its process as a loop rather than a one-time build:

1. Describe your game in your own words — no setup, no coding class, no blank screen.
2. Watch Makie write real code, live — the child sees the code being produced as the game takes shape.
3. Change anything with a single sentence — remixing is conversational.
4. Peek at the real code and learn how it works — optional, for kids who are curious.
5. Publish a play-link in one tap — sharing is built in.

The site also frames it as four simple steps: pick a starter game or a blank canvas, tell Makie what to make, play/remix/repeat, then publish and share.

Starting points

A child doesn't have to begin from nothing. They can either pick a starter game or start from a blank canvas. The site's gallery shows examples like Crowd Clash 3D, Sink City, Crownwild, Little World, Critter Clash, Crown Match, Sky Dodger, Castle Escape, Pixel Garden, Number Jam, and Dino Dash — a mix of genres that gives a sense of what's possible and gives kids something to remix rather than face an empty screen.

Who it's for

Makie is explicitly built for ages 7–15. That range shapes everything about the product:

• For kids, the appeal is speed and control — say it, see it, play it, change it. No waiting, no syntax to memorize.
• For parents, the appeal is the safety and management layer, described below.

The site positions Makie as the "build" counterpart to Askie, which it describes as the "wonder" side: "Askie is where they wonder. Makie is where they build." Both come from the same small team, with the same stated focus on child safety and warm design.

Safety and parental controls

Makie's safety model is a selling point, and the site lists specific commitments:

A few details worth noting for parents:

• Content filtering happens before building, not after — the idea is screened before a game is generated.
• There's no stranger chat, so kids aren't interacting with unknown users.
• Weekly Make Credits act as a built-in usage limit, which the site frames as keeping creation "intentional" rather than unlimited.
• Adults hold the account controls — household access, maker emails, credits, and billing all sit with the parent.

The site also links to a Parent guide and FAQ for more detail.

Sharing what they make

Publishing is deliberately low-friction: one tap creates a play-link, and friends and family don't need accounts to play. That matters for kids who want to show off a creation without asking relatives to sign up for anything.

Practical things to know before signing up

• It runs in the browser — the site describes it as having "no setup," so there's nothing to install.
• Pricing and credits are handled on a dedicated page (linked as "Pricing and credits" in the site navigation), and billing is managed by the adult on the household account. The site doesn't state specific prices in the material available here, so check that page for current costs.
• Getting started requires signing up, and the site's closing prompt is simply: "One idea is all it takes. Makie does the rest."

The short version

Makie is for kids roughly 7–15 who want to make games by describing them, and for parents who want that creativity to happen inside a filtered, ad-free, adult-managed environment. The loop is describe → watch it build → play → remix → share, with the option to read the underlying code along the way. If your child has ideas for games but not the coding skills yet — or you want a first, low-pressure exposure to real code — Makie is aimed squarely at that gap.

Makie turns a kid's description into a real, playable game in about a minute, and publishing it takes one tap. The whole process is four steps: pick a starter game or a blank canvas, tell Makie what to make, play and remix, then publish a play-link. It's built for ages 7–15, and no coding class or setup is required — friends and family can play a published link without creating an account.

Step 1: Pick a starter game or a blank canvas

You don't start from a blank screen. Makie offers two entry points:

• A starter game — browse the existing games on the site (titles like Crowd Clash 3D, Sink City, Crownwild, Little World, Critter Clash, Crown Match, Sky Dodger, Castle Escape, Pixel Garden, Number Jam, and Dino Dash) to get an idea, then build from one of them.
• A blank canvas — go straight to your own idea with nothing pre-set.

The site frames this as "Play something. Get an idea." — playing an existing game first is a legitimate way to find what you want to make.

Step 2: Tell Makie what to make

Describe the game in your own words. The site's example is a single sentence: "A dragon that catches falling stars." That's enough — Makie says a real, playable game appears in about a minute.

What happens as you describe it:

1. Makie writes real code, live, as it builds.
2. You can peek at that code to see how it works — useful for curious kids who want to learn what's underneath.

There's no menu of settings to configure first. The description is the input.

Step 3: Play, remix, repeat

Once the game exists, the loop is change-and-play:

• Change anything with a single sentence — the hero, the rules, the whole world.
• Play it to see whether the change did what you wanted.
• Repeat until it feels right.

Every idea is one sentence away, so remixing is the normal mode of working rather than a separate editing phase.

Step 4: Publish and share a play-link

One tap publishes a play-link you can send to friends and family. The people you share it with don't need accounts to play — they just open the link.

What parents should know before signing up

• Age range: built for ages 7–15.
• Content filtering: every idea passes through kid-safe content filters before anything is built.
• No ads, no stranger chat, no data sold.
• Weekly Make Credits: creation runs on a weekly credit allowance, which keeps costs visible and creation intentional.
• Household access: adults manage household access, maker emails, credits, and billing.

Pricing and credit details live on the site's Pricing and credits page — check there for current terms rather than assuming what the credits cover.

Quick reference

Makie is made by the same team behind Askie, the kids' AI learning companion — same approach to child safety and design, applied to building games instead of exploring questions.