Should my child learn robotics or coding first?

Updated · kidslab.lk

For most children under about 12, robotics first works better. A robot gives immediate physical feedback — the wheel turns or it does not — which keeps a beginner going through the part where nothing works. Pure coding suits children already comfortable with abstract results on a screen. Either way, robotics includes coding, so nothing is lost.

The real difference is feedback, not subject matter

Robotics and coding are not alternatives in the way the question implies — every robotics class is a coding class with hardware attached. What actually 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 interpreting it is itself a skill the child is still learning. In robotics the feedback is a motor that spins the wrong way, which requires no interpretation at all. 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 whose result they cannot see. They are under about 12. They have tried a coding app and drifted away from it.

That last one is common and is usually misread as 'not interested in technology'. More often it is that a rectangle moving across a screen is not a compelling enough result to justify the effort, and the same child will 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 are 12 or older. They have a specific goal — a game, a website, a script that does something for them.

A child with a concrete goal should be pointed straight at it. Motivation that specific is worth more than any curriculum ordering.

Where AI fits

AI is not a third option to be sequenced after the other two — it is what makes either of them interesting past the basics. A robot that follows a fixed rule is a machine; a robot that recognises what it is looking at and decides accordingly is where a child starts asking the questions worth asking.

In practice that means a good programme introduces AI concepts inside the robotics or coding work rather than as a separate later module. If a class treats AI as an advanced topic reserved for year two, it is probably teaching the word rather than the thing.

The honest answer about order

It matters less than the quality of the teaching and whether the child keeps showing up. A child who is enjoying a coding class is learning more than one who is correctly sequenced into robotics and bored.

The one ordering mistake worth avoiding is leading with theory in either subject. Both of these are best learned by building something that does not 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. What a robotics class adds is the electronics and the mechanical side; what it sometimes gives less of is depth in 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 for a beginner are the two things most likely to end a session in frustration rather than learning. The concepts transfer directly. Moving on to typed code usually makes sense once the blocks start feeling slow.

Do we need to buy a robotics kit?

It depends on the programme. Some supply or specify a kit; others begin with simulation and introduce hardware later. Ask before enrolling, because kit cost can quietly exceed 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.

Register for the free seminar →

More guides