Hi. I've been making a game with my seven-year-old son, and I just wanted to share a bit of my experience, because it's amazing and it's important to share amazing things. Ben loved Club Penguin and Club Penguin Island, but sadly they both got shut down. Having seen one of the tribute projects, Club Penguin Rewritten, he asked if we could make our own version. Of course, I said yes. Confession: I originally started the project with Game Maker Studio 2 because I thought the block-based approach would be easier for him, but (a) I found I had to switch to GML anyway because block-based was just painful, and (b) I think we'd added about 10 game objects when the free trial told us we'd hit a limit. So we converted to Unity and carried on. Our workflow is: Ben tells me which feature or mini-game he'd like to do next. He draws the art for it in felt-tip pen on plain paper. We scan the art in, cut out sprites in Affinity Photo, and drop them in the project. I figure out how to do stuff in Unity to make the game work, and talk him through what we're doing. Every single day Ben comes to me and says "when can we do coding?" And some days I don't have time, but whenever I do we sit down together and work for about an hour and get something done. It's totally rough and ready; if something works, he doesn't want to spend time trying to optimise it or fiddle with it. He's got too many other ideas and plans that he wants to move onto. Good enough is good enough. Seven is a little young to really get to grips with C#, but when I'm working on the code, I'll explain what everything does and sometimes get him to work things out. For example, when we were just making the penguin move around, I explained about XY coordinates and wrote the code to add to X to make the penguin move right. Then I asked him how we could make the penguin move left, and he said "take away from X?" and got a high five. There's quite a lot of mileage in that whole "how do we do the opposite thing?" approach to teaching. So far, we've made: The outside area with three doors that take you into other scenes. You can throw snowballs with a targeting reticule and they explode on impact. A pet shop where you can adopt a Puffle which will then follow you around everywhere. "The Dojo", which is a simple rock-paper-scissors style card game. "Sled Racer", which is like an infinite runner with a time limit. I'd say, in total, that's taken us less than 16 hours so far (not including the time he spends drawing the pictures). Using his art gives him a real sense of ownership of the game. He's seeing his creations move around on the screen, doing real game things. I use effects from the Epic Toon FX asset for things like exploding snowballs or snow falling off trees, but everything else is his. (I'm also using the Rewired controller asset, which is fantastic and I highly recommend it.) For me, well, I've learned more about Unity in those 16 hours of making an actual, working game from scratch than I did in a couple of years of having it installed previously and occasionally finding time to work through tutorials. Also, it turns out seven-year-olds make amazing testers. We were having an issue with the control system where when you hit the back button to exit one of the mini-games, the game exited right out. Turned out to be because loading a new scene kept the button press, so I had to write in a delay to prevent the back button from working for a second after a scene loaded. I use the same ExitManager component in each scene so I fixed it there, tested it on one scene and called it fixed, to which Ben responded "shouldn't we test it on the other doors too?" In this case it did work, but still, good call. We're now at the stage where every time we complete something we do a proper standalone build and I copy it onto his laptop so he can play it. He loves that it's a real thing, just like the other games he has on there. When it's a bit more polished (mainly UI stuff) I'm going to make a WebGL build and put it online so his friends can play it. We also make videos and upload them to YouTube every now and then, and Ben's teacher shows them in class. Apparently his friends loads of questions about the game and how we're making it, or suggest things we could add. Anyway, that's my story. I wanted to share it partly to thank Unity for giving me an easy and free* way to do this stuff with my little boy, and partly in the hopes of inspiring other parents to do something like this with their kids. * I'll buy a subscription soon, promise!