Guide

Should my child learn robotics or coding first?

By Viraj Samarasinghe & Menura Dulkith · Updated

For most children under about 12, starting with robotics works better. A robot gives instant physical feedback (the wheel turns or it doesn't), which keeps a beginner going through the stage where nothing works. Pure coding suits children who are already comfortable with abstract results on a screen. Either way, robotics includes coding, so nothing is lost.

The real difference is the feedback

Every robotics class is really a coding class with hardware attached, so the two aren't separate choices in the way the question suggests. What differs is how a child finds out whether they got it right.

In pure coding, the feedback is a number or a shape on a screen, and reading it is a skill the child is still learning. In robotics, the feedback is a motor spinning the wrong way, and nobody needs that explained. For a beginner, that difference is most of the experience.

Choose robotics first if

Your child builds things, takes things apart, or is the one holding the screwdriver. They lose interest in tasks when they can't see the result. They're under about 12. They've tried a coding app and drifted away from it.

That last one happens a lot, and people often take it to mean 'not interested in technology'. More often, a rectangle moving across a screen just isn't exciting enough to be worth the effort. The same child will happily spend two hours getting a line-following robot around a corner.

Choose coding first if

Your child already enjoys puzzle games, spreadsheets, or making things happen on a screen. They're 12 or older. They have a specific goal, like a game, a website, or a script that does something useful for them.

If your child has a clear goal, point them straight at it. That kind of motivation is worth more than getting the order of topics right.

Where AI fits

AI doesn't have to wait until after the other two. It's what makes either of them interesting once the basics are done. A robot that follows a fixed rule is a machine. A robot that recognises what it's looking at and decides what to do is where a child starts asking good questions.

In practice, a good programme brings AI ideas into the robotics or coding work, instead of saving them for a separate module later. If a class treats AI as an advanced topic for year two, it's probably only teaching the word.

The honest answer about order

Order matters less than the quality of the teaching and whether the child keeps turning up. A child enjoying a coding class learns more than a bored child who started robotics 'in the right order'.

The one mistake worth avoiding is starting with theory, in either subject. Both are best learned by building something that doesn't work and then making it work.

Related questions

Does robotics teach coding too?

Yes. A robot has to be programmed to do anything, so robotics classes teach programming as a matter of course. A robotics class adds the electronics and the mechanical side. It sometimes goes less deep into software-only topics like data structures.

Is Scratch a waste of time before real programming?

No. Block-based tools like Scratch remove typing and syntax errors, which are the two things most likely to make a beginner give up in frustration. The ideas carry straight over to typed code. Moving on to typed code usually makes sense once the blocks start to feel slow.

Do we need to buy a robotics kit?

It depends on the programme. Some supply a kit or tell you which one to get. Others start with simulation and bring in hardware later. Ask before you enrol, because the kit can quietly end up costing more than the course fee.

See a real session before deciding

kidslab.lk runs a free introductory seminar for children aged 9–14, live online across Sri Lanka. No obligation to enrol — it exists so you can answer most of the questions above for yourself. Where children join from.

Register for the free seminar →

More guides