# What Kids Actually Build at Codeyoung's Summer Coding Camp Author: Team Codeyoung Author URL: https://www.codeyoung.com/blog/author/team-codeyoung Published: 2026-08-06 Category: Coding For Kids & Teens Category URL: https://www.codeyoung.com/blog/category/coding-for-kids-and-teens Meta Title: What Kids Build at Codeyoung Summer Coding Camp Meta Description: Real projects, by age and track: what children actually build during Codeyoung's Summer Coding Camp in 2026, from first Scratch animations to AI classifiers and live websites. Tags: Summer learning program, Coding Summer Camp, Coding For Kids Tag URLs: Summer learning program (https://www.codeyoung.com/blog/tag/summer-learning-program), Coding Summer Camp (https://www.codeyoung.com/blog/tag/coding-summer-camp), Coding For Kids (https://www.codeyoung.com/blog/tag/coding-for-kids) URL: https://www.codeyoung.com/blog/what-kids-build-summer-coding-camp ![what kids build at summer coding camp: montage of a Scratch game, a Python script, and a website built by children at different ages during summer coding sessions](https://prod.superblogcdn.com/site_cuid_clvc4016q001j13bhaleswmt1/images/6-1786014588433-compressed.jpg) ## What Kids Actually Build at Codeyoung's Summer Coding Camp The most common question parents ask before enrolling in a summer coding programme is some version of: "But what will they actually make?" It's the right question. "Your child will learn to code" and "your child will build three complete projects that run on their device, that they wrote themselves, and that they can share with a link" are very different promises. This guide answers the question specifically, by age group and by coding track. Not in terms of concepts covered or skills introduced, in terms of actual projects: what they look like, what they do, how the child feels when they run them for the first time, and why those specific projects matter for what comes after. ## Key Takeaways - Every Codeyoung summer camp session produces a contribution toward a real, runnable project: not exercises, not tutorials, not certificates. Actual code that does something. - By the end of an 8-week summer camp (2 sessions/week), most children have 3 to 5 complete projects they can run, share, and explain. - The projects get more ambitious each session: not because the instructor sets harder tasks, but because the child's capability grows and they ask for more. - The difference between a Scratch game and a Python app is not just technical, it's motivational: children who see progressively more complex things emerging from their own code want to continue long past summer. - Every project built in summer camp has a "show someone" moment: a parent, a sibling, a friend, and that moment is consistently the most powerful driver of continued engagement. ## What Children Build on the Scratch Track (Ages 6 to 10) Scratch is the starting point for children aged 6 to 10 with little or no prior coding experience. It uses blocks rather than typed code, removing the spelling and typing barrier and letting children focus entirely on the programming logic: sequences, loops, conditionals, events, variables. Over an 8-week summer (16 sessions at twice weekly), a typical Scratch journey looks like this: Typical Scratch Project Progression Over Summer Camp Week Project What the Child Learns The "Show Someone" Moment Week 1 to 2 Animated scene: a character the child designed moves, speaks, and reacts to a click Sequences, event handling, sprite editor, basic motion and sound "Look, when you click on it, it says my name!", typically shared with a parent on the same day Week 3 to 4 Simple platform game: a character moves left and right, jumps, and avoids an obstacle Conditionals, collision detection, keyboard controls, basic physics Child asks a sibling to play it. Sibling plays it. Child revises it based on feedback. Real product cycle. Week 5 to 6 Multi-level game with a score system: the game tracks points, increases difficulty, and has a "you win" screen Variables, loops, score logic, game state management, broadcast messaging between sprites Child shows it unprompted at dinner: "I made this and it keeps score by itself." Week 7 to 8 Child's own original project: usually a game, quiz, or interactive story in a world they invented Independent project planning, applying all previous concepts, debugging independently, creative decision-making Child asks to share the Scratch link with their class before school starts. The project is genuinely theirs. The final project in Week 7 to 8 is the most significant. It's the first project the child chose, planned, and built without a specific instructor brief. The game world, the characters, the rules, all theirs. This is the transition from "completing coding activities" to "being a creator who uses code." ## What Children Build on the Python Beginner Track (Ages 10 to 13) Python is text-based: the child types every character, and it's the language that underlies almost every significant real-world application of coding: data science, AI, web back-ends, automation. Starting Python at ages 10 to 13 builds the foundation for all of these. A beginner Python journey over an 8-week summer (16 sessions): - **Sessions 1 to 3, First text programmes:** A programme that asks for the user's name and produces a personalised greeting. A times-tables generator. A simple calculator. These are small but the principle is enormous: the child gives the computer instructions in text, and the computer follows them. The surprise at how few lines produce a working result is real and universal. - **Sessions 4 to 6, First game:** A number-guessing game. The computer picks a random number; the player guesses; the programme says "too high," "too low," or "correct!" with the number of attempts displayed. Children revise this game obsessively: adding a limited attempts mode, a difficulty selector, a high-score tracker. Each revision is a new programming concept applied. - **Sessions 7 to 10, Quiz project:** A quiz on a topic the child chose. Ten questions on their favourite game, a TV show, history, science, their choice entirely. The child writes the questions, the programme delivers them, checks the answers, and gives a final score with feedback. This project is shareable by simply running it: "Ask me these questions, I made it." - **Sessions 11 to 13, Text adventure:** An interactive story where the player's choices determine the outcome. The child writes the story, the branching paths, the descriptions. The code implements the story they created. This is the project that makes non-technical parents go quiet for a moment: "You built a game that tells a story?" Yes. Entirely in Python. Entirely by your child. - **Sessions 14 to 16, Pygame introduction:** Moving from text to graphics. A bouncing ball. A moving player. The beginning of a real 2D game. By the end of summer the child has a visual programme on screen that they control: a bridge to the full Pygame game development track in the school year ahead. ## What Children Build on the Web Development Track (Ages 11 to 16) Web development is the most immediately shareable track, everything built is a webpage with a live URL. Over an 8-week summer, a typical journey: - **Weeks 1 to 2:** A personal homepage. Name, a short bio, a photo, styled in CSS. Simple but live in a browser and structurally correct. The moment a child sees their own words and their own design rendered in Chrome is a specific kind of satisfaction that nothing else produces quite the same way. - **Weeks 3 to 4:** Multiple linked pages. An about page, a hobbies page, a contact form. Navigation between pages. CSS layout with flexbox. The site is starting to look like something a real organisation would publish. - **Weeks 5 to 6:** JavaScript interactivity. A to-do list that adds and removes items. A colour-picker that changes the page background. A quiz with immediate feedback. The site can now do things rather than just display things. - **Weeks 7 to 8:** Deployment to GitHub Pages. The site has a real URL. The child shares it. Teachers, relatives, friends, anyone with the link can visit it. This is the moment when "I made a website" stops being a metaphor and becomes a fact with evidence. ## What Teenagers Build on the Python AI/ML Track (Ages 13 to 17) The AI track is the most ambitious and produces the most striking outputs. Prerequisites: solid Python foundations from previous sessions or the school year. - **Early sessions:** Data exploration. Loading a real dataset (movie ratings, housing prices, student marks). Analysing it with pandas. Visualising patterns with matplotlib. Understanding what the data tells us before building anything with it. - **Mid-summer:** First classifier. A spam email detector or sentiment analyser, trained on real labelled data, that can take new text input and predict a category. The child writes the training code, evaluates the accuracy, and can explain what the model is doing and why. - **End of summer:** An AI project of the child's choosing. An image classifier that recognises objects. A recommendation system for their music taste. A text generator. Something that uses ML in a context that matters to them specifically. The AI track produces the projects that consistently generate the most impressive reactions, "you built something that learned?", and the most substantive university application portfolio material for students in this age range. Want to see what your child builds in their first session? Every track starts with a free trial class that produces a real, runnable result before the session ends. [Explore the Summer Coding Camp →](https://www.codeyoung.com/summer-camp-coding) ![child showing their completed coding camp project to a parent: a Pygame game running on screen, both looking at it with pride](https://prod.superblogcdn.com/site_cuid_clvc4016q001j13bhaleswmt1/images/7-1786014613163-compressed.jpg) ## Why the Projects Matter Beyond the Summer The projects built over summer are not just summer outputs. They are portfolio pieces for school applications and university personal statements. They are conversation starters in computing classes. They are the evidence a child has when they want to claim, credibly, that they can code. For older teenagers, a Codeyoung summer AI project sits on a GitHub profile that university computer science departments actively look at during application season. More fundamentally, the projects are the intrinsic motivation that sustains coding through the school year. A child who is proud of what they built over summer is far more likely to continue building through September, October, and beyond: not because they've been told to, but because they're a person who makes things with code now. That identity shift is the most durable outcome of a strong summer coding camp. For more on what coding produces beyond the summer, see [Kids Who Code: Real Stories and What the Journey Looks Like](https://www.codeyoung.com/blog/kids-who-code-student-stories/), [Is Coding a Good Career for Kids?](https://www.codeyoung.com/blog/coding-career-for-kids/), and [Coding Summer Camp for Kids: What to Expect Online](https://www.codeyoung.com/blog/coding-summer-camp-for-kids/). ## Frequently Asked Questions: What Kids Build at Summer Coding Camp ### Do children actually build complete projects, or just partial exercises? Complete projects. Every session contributes toward a runnable, demonstrable project that the child owns. Sessions are structured around clear goals ("today we finish the scoring system") and end with something working: not with an exercise completed and a new exercise begun. By the end of summer, children have 3 to 5 projects they can run, share, and explain. ### Are the projects the child's own or do they follow a tutorial? The child's own. The instructor guides the approach and teaches the concepts, but the choices about what the game is about, what the quiz covers, what the website says, and what the AI project does are the child's. The code is the child's, not a copy of an instructor's demo. The instructor teaches the technique; the child applies it to their own project. ### Can parents see what their child is building? Yes. Scratch projects have a shareable link at scratch.mit.edu that anyone can visit. Python projects run on the child's device and can be shown directly. Web development projects are deployed to GitHub Pages with a live URL. Parents see finished projects, not just hear about them. ### What happens to the projects after summer? They stay on the child's device, on their Scratch account, or on their GitHub profile, permanently. Children regularly continue working on summer projects into the school year, adding features, improving the game, extending the website. The projects don't end when summer does. ### What if my child has already done some coding and wants a more advanced project? The camp calibrates to each child's current level from the first session. A child who already has Python foundations would skip the beginner weeks and go straight to a Pygame game, a web application, or the AI track, wherever their current level positions them. There is no fixed programme that all children follow regardless of where they start. ### What other summer camps does Codeyoung offer alongside the coding camp? Alongside coding, Codeyoung runs summer camps in [English](https://www.codeyoung.com/summer-camp-english), [maths](https://www.codeyoung.com/summer-camp-math), and [Digital SAT preparation](https://www.codeyoung.com/summer-camp-sat). Many families run maths and coding sessions in the same week, as the two subjects reinforce each other strongly. ### How do I get my child started on the Summer Coding Camp? Visit [Codeyoung's Summer Coding Camp page](https://www.codeyoung.com/summer-camp-coding), choose the relevant age and track, and book a free first session. The child codes something real and runnable in that first session, so you see exactly what the programme delivers before any commitment. ## The Best Way to Understand What Kids Build Is to Watch One Session Reading a list of projects is one thing. Watching your child run a programme they wrote, seeing their face when a function they spent 20 minutes debugging finally works, is another. That moment is available in the very first session, and the first session is free. The projects described in this guide are not aspirational marketing content. They are what Codeyoung's summer camp students build, every summer, across thousands of sessions. The Scratch game in Week 5. The Python quiz the child chose the topic for. The live website with a URL to share. These are real outputs, produced by real children, because a qualified instructor working 1:1 with one child for 45 minutes can get a remarkable amount built. See every coding track and age range at [Codeyoung's Summer Coding Camp](https://www.codeyoung.com/summer-camp-coding) and start building. ### Book a free session and see what your child builds in 45 minutes. Codeyoung's Summer Coding Camp: real projects, by age and track, for children aged 6 to 17. First session free. [Enrol in the Summer Coding Camp →](https://www.codeyoung.com/summer-camp-coding) --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---