WHY2MAKE ACADEMY

For parents

The Academy is preparing to open on 1 January 2027 for ages 7–9, 10–12 and 13–15. Here is what you can already try and how we plan to organise learning.

Hush, the plush robot and keeper of the Academy, opens his arms

The workspace we are building

In the Academy under development, commands change a scene: a courier crosses a city and code turns on a light. Hush helps spot mistakes. Saved projects, learning routes and a parent dashboard are being prepared; today this public site offers standalone mini-scenes.

One system comes in three familiar layouts, so your child won’t get lost at any computer — at home, at school, at grandma’s.

What we plan to show parents

evidence, not gradesWhat your child has learned to do

Not “85 points”, but “writes an if condition, finds a bug and fixes it, saves and shows a project”. Every item is backed by their own work.

projectsEverything they’ve made

Saved projects and their versions: what your child changed, the solution they found and what they want to try next. These Academy features are in development.

no rankingsNo competition

Kids aren’t compared with each other here. Only yesterday’s project with today’s.

Age and path

7–9

Planned for launch: plain-word commands, sequences and first conditions in the Firefly Garden.

10–12

Planned for launch: a courier route, conditions and loops. Learning commands using Python syntax.

13–15

Planned for launch: music, light and code. Projects that call for breaking an idea into parts.

16–17

Later stage: engineering diagrams, electrics and logic.

First launch: 1 January 2027 in Russia, for ages 7–9, 10–12 and 13–15. Ages 16–17 will follow later. Public examples need no purchase or registration.

The words of code become their own

Code speaks English: if, light, robot. Your child doesn’t memorise these words — they use them, because they make something happen on the screen. That’s how they become their own. It isn’t an English lesson, but these are the first English words a child applies rather than repeats.

The intelligent assistant we want to build

We are preparing an assistant that explains, asks questions back and teaches children to check answers. Generative AI is not yet part of public learning: answer review, topic boundaries and parental controls still need testing before launch.

explainsAnswers “why?”

Not “do it like this”, but “look what happens if…”. Your child understands rather than repeats.

asksHands the question back

When your child is stuck, the assistant doesn’t solve it for them — it hints where to look, and waits.

teaches checkingAI can be checked too

Your child learns to compare the assistant’s answer with the result on the screen. That’s how the habit is born of not taking anyone’s word for it — human or machine.

Hush on this site currently follows a script and speaks prepared lines. He does not have open conversations with children.

Safety and data

Frequently asked questions

What age to start?

From seven. Separate routes for ages 7–9, 10–12 and 13–15 are planned for opening. Ages 16–17 belong to a later stage.

Do I need a powerful computer, or to install anything?

The full Academy is planned for computers and tablets with a sufficiently large screen. Phones will support the parent dashboard; a small screen is awkward for learning. Public examples can already be explored.

Windows, Mac or Linux?

Any. Inside the Academy your child picks the layout they’re used to — and the same system stays at hand on any computer.

How much time does it take?

We plan short tasks with saved progress. Families will be able to choose a pace that suits the child and take breaks. Session length should not become a compulsory target.

What if my child can’t do it?

That’s fine — it’s built into the whole idea. A mistake here isn’t punished with a score; it gets fixed: the code changes, the result changes. Hush doesn’t rush you in that moment.

Is this a replacement for school or a club?

No. It’s a workshop where your child makes their own things — alongside school, not instead of it. Plenty of what’s here will come in handy in computer science classes and in projects.

We’re making this for our own children. And testing it on them — before we show it to yours.