Should I choose 1:1 or a small group?
1:1 maximises pace and shy kids. Small groups add peer energy if the mentor still gives every child airtime. Avoid large webinars for absolute beginners.
Parent answer guide
Match four things: age/typing readiness, the outcome they want to show (game, website, robot, AI project), live mentor help versus recorded videos, and a clear session count. Then take a short trial before a long package. Brand names matter less than weekly projects and someone who can debug with your child.
Related courses, sibling answer guides, and deep dives that build topical authority around how to choose a coding course for kids.
| Path | Typical ages | What they build |
|---|---|---|
| Want games, hate typing | Class 3–5 | Start Scratch |
| Want apps, AI, school CS | Class 5–12 | Start Python |
| Want shareable websites | Class 4–12 | Start Web |
| Want wires & motors | Class 3–12 | Start Robotics |
| Want AI safely | Class 3–12 | Literacy → Python → LLMs |
Use the checklist, shortlist one course, then book a local-currency 60-minute session (adjusted on enrolment). Watch whether your child leaves with a tiny win and clear next steps — that is the signal.
1:1 maximises pace and shy kids. Small groups add peer energy if the mentor still gives every child airtime. Avoid large webinars for absolute beginners.
Enough to finish a real project — typically a structured 30-session syllabus for Scratch, Python, web, or robotics at GeekashramJr — not a three-class teaser that ends mid-skill.
Recorded is fine for revision. For a first language, live help when the child is stuck is usually worth more than a huge video library.
GeekashramJr makes the choice concrete: short a local-currency 60-minute session (adjusted on enrolment), clear 30-session course maps, small live batches, and mentors who place kids on Scratch, Python, web, AI, or robotics — then prove it with a project.
Browse all courses →Try a session →Is live online worth it? →