candyandfrank ▸ MAKER
BUG HUNT / DEMO
BUGS FIXED 0 ♥♥♥
A touch screen, ten side lights, a speaker and a battery base. Your child puts it together, programs all three faces and takes it home.
Every game your child makes has ideas that engineers use every day. They are learned by changing them and watching what happens.
Speed, gravity and jump height are numbers. Change one and the whole game feels different.
Screen shake, sparks, sound and a buzz in your hand: tricks that change how a game feels, not its rules.
A world far bigger than the screen, stored as text, with a camera that follows you.
Ghosts with moods and a search for the shortest path. Your child writes a ghost of their own.
A four-letter code builds a whole dungeon, the same one on every machine.
A program that understands typed commands, and an AI character that can be wrong.
Numbered messages over radio, answered and sent again when lost: how the internet works.
Trigonometry draws a 3D maze. Then the race to make the code run faster.
The machine runs only what your child built. There is no feed to scroll and no other game one tap away, so the time goes into making, not watching.
Dash: the whole level is one line of text. Add a spike, then beat your own level.
What do you play, what do the buttons do, how do you win and lose? A vague card gets questions back, not code.
A minute later there is real Python, with a walkthrough of what each part does.
Every number that matters sits at the top of the file. Change it, predict, play, and report what broke.
One click down a USB cable and it is a real game you can hand to a friend.
Once a week after school, in a group of ten. Your child assembles the pocket computer, makes games and tools on it, and shows them to the family at Demo Day.
Camp families log in here for every session's page and the Build Station.
For children who already have the machine: the AI build crew, new game templates and the arcade, month by month.
Log in, or create an account to join.
No. The first session starts with the game they want to play. They finish it having read real Python and changed it on purpose.
Real Python, running on real hardware. The file your child edits is the file the handheld runs.
Three gates. A vague design card gets questions instead of code. A rework needs a bug report that names what is broken. And the numbers that make a game feel good are left for your child to tune by hand.
A Windows or Mac computer with Chrome or Edge, and a USB-C data cable. Nothing is installed on the computer.
Use Camp log in above, with the email and password you set when you booked. Each session's page and the Build Station are there.