Robotics classes for kids in the Philippines work the build and the code together, one tutor with one learner, at home or online. DepEd lists no robotics subject, so this is where a young builder learns why correct logic still turns left on tile: a wheel slips, a battery sags, one motor pulls harder. Solving that gap is the craft.
105+
Active tutors
400+
Learners taught
105+
Active tutors
400+
Learners taught
What is
One-to-one lessons in building and programming machines that do something physical: move, sense, grip, respond. It shares programming with coding but adds the part coding cannot simulate: a real world that does not do what the model says it will. The learner's job becomes closing the distance between the two.
Key Points
Building and programming, side by side
Goes past following the instructions in a kit
Sensors, motors and why they misbehave
Not a DepEd subject and not on the report card
A from-rate by level, hardware priced on its own
Hardware makes this one of the few programs where the choice really matters
Workable, and it requires the learner to have the hardware at home. A tutor can see the build on camera, read the code on a shared screen and talk a learner through a fault, but cannot hold the wire that is not quite making contact.
Better for the early months and for younger learners, because a large share of robotics problems are physical: a loose connection, a motor mounted a few degrees off, a chassis that flexes. Those are much faster to find in the same room.
Past the kit, into the part where it does not work
Building the model on the box is worth doing once. Everything after that comes from modifying it, breaking it and making it do something it was not designed for.
A learner who cannot tell a wiring fault from a logic fault will rewrite correct code for an hour. Knowing which half is broken is the skill this subject actually builds.
A robot works when it works every run. We count failures across repeated runs, which turns nearly working into a specific, fixable problem.
Readings drift, spike and disagree, and programs written as though they do not fail in the real room. Learners watch the raw numbers before writing anything on top of them.
The stage with no instructions and no correct answer is where most of the learning lives. It is uncomfortable, it is where we are heading, and we do not rush a learner into it. Any learner can switch to a different robotics tutor at any stage, at no charge, and the build and its code travel along.
A from-rate for the level, the setting and the area, confirmed in writing before the learner opens a kit, with the hardware billed separately.
Not by age, because a determined nine-year-old and a cautious fourteen-year-old land in the same place
The starting point, and not the destination
Assembling a model from a kit's steps. Genuinely worth doing (it builds familiarity with the parts and the patience to follow a sequence), and it is where a great many robotics classes stop, which is the problem.
Subjects
Focus Areas
Where robotics actually starts
The robot works once and then does not. This is the stage where a learner meets slip, drift, battery sag and tolerance, and it is the first genuinely hard idea in the subject: the program did not change, so something outside the program did.
Subjects
Focus Areas
The robot stops being a sequence
Adding sensors turns a fixed routine into something that responds. It also introduces the least intuitive part of the subject: sensors return messy, drifting, occasionally nonsensical numbers, and the program has to be written to cope with exactly that.
Subjects
Focus Areas
No instructions, no model on the box
The learner decides what it should do and then finds out what that costs. The most valuable stage and the least comfortable one, because for the first time there is no correct answer to check against.
Subjects
Focus Areas
Programming and hardware together, because separating them is what produces robots that only work on paper
A learner who can program but cannot check whether the motor is actually receiving power will spend hours rewriting correct code. Half the skill here is knowing which half is broken.
Two identical motors given identical instructions do not produce identical movement. Meeting that early, and dealing with it deliberately, is the difference between a robot that drives straight and one that curves.
Online Tutoring
Anywhere with a usable connection, provided the hardware is at your endWorks well for learners who can already handle their own kit. Code shares on screen and a build can be shown on camera, though a loose connection is genuinely harder to diagnose at a distance than anything else in the subject.
Timezone: Philippine Standard Time (UTC+8)
In-Person Tutoring
At home, with the parts box on the tableA robotics tutor comes to the house with an eye for the hardware. Being in the room matters more for this subject than for one taught from a textbook, because of the box of parts on the table: a loose header pin or a motor wired backward is something a hand can find in seconds and a camera often cannot. Tell us your area and we match the robotics tutor nearest you, and lessons can run online everywhere else while you wait.
Five situations, and the build each one starts with
Already curious about how objects work and usually more interested in the mechanism than the screen. Robotics gives that instinct somewhere to go and something to finish.
Recommended:
6
common pitfalls
Most of them look like progress while they are happening
01
Why it happens
A kit with good instructions produces a working robot and a proud photo, and the builder has practiced following a sequence. That is a real skill of its own, separate from robotics, and the gap only shows when the instructions run out.
Our solution
After the first build, change something. Make it carry a load, turn a different way, or react to something. The moment the instructions stop covering it, the learning starts.
02
Why it happens
When a robot misbehaves, code is the part a learner can see and edit, so that is where they look. Meanwhile the connector is loose or the battery is at half, and no amount of rewriting will touch it.
Our solution
Teach the split early: is this code, wiring, mechanics or power? Checking power first costs ten seconds and saves entire afternoons.
03
Why it happens
Under frustration, a learner adjusts the speed, moves the sensor and edits the logic together. It sometimes works, and they learn nothing from it, because there is no way to know which change mattered.
Our solution
One change, one test. Slower for twenty minutes and dramatically faster over an afternoon, and it is the single habit that most separates learners who improve from learners who thrash.
04
Why it happens
A sensor gives a number, and numbers look authoritative. Then the light changes, the surface changes, or the reading spikes for no reason, and a program that trusted it does something absurd.
Our solution
Watch the raw readings before writing logic on top of them. Learners are always surprised by how much a supposedly steady value actually moves.
05
Why it happens
A robot that works on the third attempt is treated as working. Reliability is invisible in a demonstration and is the whole game in a competition, and the difference is not discovered until the day.
Our solution
Run it ten times and count the failures. The number is usually a surprise, and it turns a vague sense of nearly working into something that can be fixed.
06
Why it happens
A wheel that drags or a frame that flexes can be compensated for in code, and it feels clever. It also makes the program fragile: it now describes a specific broken robot, and it stops working the moment anything is adjusted.
Our solution
Fix the physical thing when it is the physical thing. Software compensation is a legitimate tool and a bad habit when it replaces a screwdriver.
The first one is the big one, and it is uncomfortable because the child is visibly busy, visibly building, and visibly finishing things.
One tutor working the build and the code with one learner. The kit is priced apart from this.
From
₱400 / hour
| Home visit, Metro Manila | ₱550 / hour |
| Online | ₱400 / hour |
| Home visit, provincial areas | ₱400 / hour |
Per hour, one tutor with one learner. Home visits run at least 1.5 hours. Packages: 12 hours at 5% off, 24 hours at 10% off.
That opening figure covers the youngest grade band on this page; a Junior High or Senior High learner building the same robot pays the rate for their own grade band. A home visit inside Metro Manila costs more per hour than the identical lesson online, because it carries the tutor's travel across the city; a home visit outside Metro Manila is charged at the online rate. Robotics tends to run as a weekly session, since a single sitting needs room to set the hardware up, run a test, fix what the test found, and pack everything away, on top of the actual building and coding. Longer packages cost less per hour, so a 12-hour or 24-hour block is worth asking about once the learner has settled in. The board, motors or sensors the learner needs are a separate figure, worked out once we know which kit fits.
The equipment question comes first, because it should
Yes, robotics needs something physical to build with, though the entry point is cheaper than most people expect. A basic mechanical set aimed at a nine-year-old costs a fraction of what a microcontroller board and a handful of sensors run, and both are legitimate places to begin, depending on whether the learner gravitates toward moving parts or toward wiring and code. Tell us the age and which of those two pulls harder, and the recommendation that comes back is specific: which board or set, roughly what it costs, and whether starting small and upgrading later suits the learner better than buying everything on day one.
Other questions
An old kit gathering dust, a robot mid-build, a school competition team, or nothing yet: each of those is a fine place to start. Tell us how the learner reacts when a build refuses to cooperate, since that says more about readiness than age does. Someone here reads what you send and comes back with where to begin and what hardware it calls for.