Worldwide · GST / AST

Codeoko

Ages 11–14

App Builders

Ages 11–14 write Python, websites, and games — with tests a mentor can fail and a site a parent can open on a phone.

See student projects

Class

1 : 4 · 4 children

Term

24 studios · 12 weeks

Weekend

Friday + Saturday

Length

60 minutes each

Who it is for

11–14s ready to build things a parent can open — a site, a game, or a small data app. Prior code helps; it is not required. A web-focused 1:1 track is available when placement says so.

They leave the sandbox. A page has to open in a browser. A game has gravity. A test can fail for a real reason. Same tiny class: four kids, one engineer — Friday and Saturday.

How the term runs

Weekend studios, two days a week.

Fri & Sat · 17:30–18:30 · AST / GST · 60 minutes

30–60 minutes between studios · English · live online.

Friday

New piece: a page, a test, a fetch, or a jump.

Saturday

Mentor tries to break it. They fix what broke.

Show

Twelve minutes at term end, no slides. Parents can watch.

Software they grow confident in

Not a logo list. Each line is the level they reach by the end of the term — and what that means in practice.

Python 3

Intermediate

Functions, lists and dictionaries, edge cases, reading errors. Not async web frameworks.

pytest

Basic → Intermediate

Write a test, watch red → green, and explain why it failed.

HTML5 + CSS3

Intermediate

Semantic pages and mobile-first layouts that hold on a phone.

JavaScript (ES6 basics)

Basic → Intermediate

Events, DOM updates, fetch, and a first async/await.

VS Code · Git · GitHub

Basic → Intermediate

Commit, push, README — mentor can open the same repo.

Netlify / Cloudflare Pages / Vercel

Basic deploy

A public URL for the portfolio a parent can open.

Figma (read) · JSON / mock API

Basic

Read a layout; fetch ready data. Not PHP or MySQL at this age.

Three projects this term

At each stage the mentor helps them choose. By showcase night, three builds exist that the family can open.

Project 1

Studios 1–6

Quiz, shop calculator, or timer (tested Python) · Web track: Portfolio v1

They ship: Runnable repository with tests and a clear README

Project 2

Studios 7–12

My Portfolio, local guide, or club page

They ship: Responsive site with a public URL

Project 3 · Capstone

Studios 13–24

Cohort: Sky Hopper-style game or Color Rover sim · Web track: Data Card App then Study Hub / utility

They ship: Live URL or runnable release + README + 12-minute defence

Term shape

How the twelve weeks move — foundations, builds, polish, showcase. Lesson-by-lesson teaching plans stay with the mentor.

  1. 1

    Python that can fail a test

    Studios 1–6

    Setup, Git habits, functions, pytest, and the first shipped utility.

  2. 2

    A site that opens

    Studios 7–12

    HTML, responsive CSS, light JavaScript, reading a Figma frame, and a live deploy.

  3. 3

    Third build

    Studios 13–20

    Game systems or API-backed web work — data outside the logic, polish, and debug.

  4. 4

    Portfolio & demo day

    Studios 21–24

    Link every build, document honestly, rehearse, and present to family.

By the end of the term

What they can do on their own

Open a live link they deployed, show the repository, change one feature without breaking the rest, explain one design choice in twelve minutes, and (cohort) show a test that fails for a real reason.

  • A tested Python utility (quiz, shop, or timer) in a clean repository
  • A responsive personal site live on the public web
  • A third build: original game or data-driven web app — with README and show-and-tell

Inside the studio

Software that has to survive contact with reality.

Studio format

  • Studio size

    1 engineer-mentor · 4 builders · live pair debugging

  • Cadence

    Friday + Saturday · 24 studios over 12 weeks · GST / AST

  • Language

    English studio · professional naming and comments

  • Bar

    It must open, run, and fail tests honestly — decoration is not enough

Craft in the room

  • Python + tests

    Functions, lists, and pytest. A red test is a teacher — they learn to read it and fix the cause.

  • Web craft

    HTML structure, CSS that holds on a phone, light JavaScript — a personal site on localhost.

  • Game systems

    Pygame with gravity, jump, collision, and a score that only rises when earned.

  • Sensors & motion

    Simple robot / sim logic: read a value, branch, move — green means go, red means stop.

Mentors try to break the work on purpose. The child repairs it. That is how professional standards enter at eleven — not through certificates.

Project briefs

Open the live demos below. These are the kinds of builds in App Builders — games, sites, and tools a family can try on the call.

Python game

Sky Hopper

Gravity, jump, pipes. A side-scroller they write — not download.

PythonPygameGravity
Project page →

Robot challenge

Color Rover

Green go, red stop, blue turn — code that moves something.

PythonSensorsMotors
Project page →

Browse all live demos →

First CodeAI Engineers

Ready when you are

Let them learn to code — for real.

We’ll check App Builders is the right fit for their age and what they like to make.

See programs
App Builders Coding Program for Ages 11–14 | Codeoko