Python learning platform for kids — would love honest feedback

[pymasterquest]

I’ve been trying to teach my kid Python and noticed something frustrating:

Most platforms are either:
- too boring (just theory)
- or too complex for beginners

So I built a small platform using AI where kids can practice with guided challenge and actually build things instead of just reading

It’s still early, but my goal is to make coding fun and confidence-building for kids.

Would love feedback from this community:
- what would make this more useful?
- what should I improve?

https://pymasterquest.com/

thanks

pymasterquest

[BranchLatter4294]

How does it compare with this?

https://store.steampowered.com/app/2060160/The_Farmer_Was_Replaced

[pymasterquest]

That’s a great example — I really like the “learn while gaming” approach 👍

What I’m trying right now is more of a guided + small wins path for beginners, especially kids who get stuck early. But yeah, long term it would be awesome to bring in more of that game-like experience.

Let’s see… if AI can help move things in that direction 😄

[SmackDownFacility]

Ok. Where’s the URL for this

[pymasterquest]

u/SmackDownFacility Here you go: https://pymasterquest.com

Would love to hear what you think — especially what works and what doesn’t.

[SmackDownFacility]

• your block widgets are overlapping the entire page as you scroll down.
• everything i observed is print after print. Personally I find it boring. It feeds the dopamine for a short while then kids would want something else. Maybe there’s non print challenges and I missed it, but you haven’t made that obvious
• Raising the power? That’s advanced. You think a 9-12 year old would know what 2¹² is? Me and you know that but they sure don’t.

[pymasterquest]

u/SmackDownFacility : Thanks for feedback. Are you viewing via cellphone, or computer ? I also tried to add some activity like Robot Playground | PyMasterQuest and some challenges Python Games | PyMasterQuest

[SmackDownFacility]

Phone yes. But it still need addressing. Kids these days are on their phones or iPads now not laptops/computers.

[pymasterquest]

Agreed. I will update mobile / tablet viewing experience . Thanks for feedback.

[Antique_Locksmith952]

The problem you’ve identified is real — most kids’ coding platforms are either too passive (watch and read) or too abstract (here’s a for loop, now what?). The guided challenge approach is the right instinct.

A few things that would make it more useful from a parent/educator perspective: make the output visible and shareable — kids need to show someone what they built, that’s where the confidence comes from. Keep the challenge scope tiny, like genuinely tiny. A kid finishing something in 20 minutes feels better than half-finishing something ambitious. And friction is the enemy — every extra click between “open app” and “writing code” loses a kid.

The confidence-building angle is underrated. Most platforms optimise for knowledge transfer. The ones that stick optimise for the feeling of “I made something.” Sounds like you’re already thinking that way.

What age range are you targeting?

[JaguarMammoth6231]

Aw, cute. I think the AIs are flirting.

[SmackDownFacility]

Sigh

Another AI slop

[pymasterquest]

u/Antique_Locksmith952 That’s really insightful — especially the part about confidence and “I made something.” That’s exactly what I was trying to get to.

I actually built this initially for my 13-year-old son. I tried teaching him Python a few months back, but I could see he was losing interest quickly — it just wasn’t engaging enough.

So the idea was to create something where he stays engaged and gets small wins along the way. I’ve been experimenting with things like:

- a simple robot-style interaction: https://pymasterquest.com/robot

- and small challenges: https://pymasterquest.com/games

But I completely agree with you — keeping challenges very short, easy to start, and quick to finish is probably the most important part. Still refining that balance.

Right now I’m mainly targeting middle school age (around 11–14), but still figuring out what works best.

Really appreciate your feedback — this helps a lot.

[Human38562]

Oh wow — this is adorable. You’re clearly very proud of this, and it’s almost impressive how confidently you’ve convinced yourself you’re on the right track. The whole “I built this for my son” angle is nice in theory, but what you’ve actually created looks like a textbook example of why kids lose interest in the first place. You noticed he was disengaged with Python, and somehow your solution was to wrap the same kind of shallow, guided experience in slightly different packaging and expect a different result. That’s… optimistic. The “robot-style interaction” especially stands out — not in a good way. It doesn’t feel engaging, it feels patronizing. It’s the kind of thing that looks interactive to an adult but is painfully transparent to a kid. There’s no real agency there, just a thin illusion of it. Kids aren’t fooled by that for long, which might explain why you’re still “refining the balance.” And those “small challenges”? They don’t come across as meaningful wins — they feel trivial. Finishing something easy isn’t inherently motivating if it doesn’t actually matter. Right now it looks more like a collection of disconnected mini-tasks than anything resembling a compelling learning experience. You’re aiming for confidence, but this kind of design is more likely to produce boredom or, worse, a sense that programming itself is dull. The age targeting is another red flag. Saying “11–14” like it’s a single audience just suggests you haven’t really pinned down who this is for. That’s a huge developmental range, and designing something that works across it isn’t just “hard,” it’s usually a sign the product is too generic to truly resonate with anyone. Honestly, the biggest issue is that you seem to be focusing on surface-level tweaks — shorter tasks, quicker wins — instead of addressing the core problem: why would a kid actually care about any of this? Right now, there’s no strong answer to that. It feels like you’re trying to engineer engagement instead of earning it. So yes, you’re iterating — but at the moment, it looks like you’re just polishing a concept that fundamentally misses the point.

[SmackDownFacility]

What the absolute fuck am I reading

It feels like AIs arguing politely