Skip to content

For teachers

Robonine Lab was built for one learner and one arm. It teaches that learner extremely well, and it holds them to a real standard: nothing is passed by clicking next, and most steps are graded by watching what the arm actually did.

It has no class management. Read the next section before you plan anything, so that nothing here surprises you in week one.

What the platform does, and does not, provide

A structured, graded 12-module course on a real arm Yes
Works with no hardware, for part of the course Yes, the virtual arm
One arm shared between learners One at a time, remote session
A completion certificate you can collect PDF, per learner
Teacher account or role Does not exist
Classes, groups, rosters, invite codes Do not exist
A dashboard showing your group's progress Does not exist
Time on task, quiz scores, attempt counts Not recorded at all
Assigning, reordering or hiding modules The order is fixed
Setting homework inside the platform Does not exist
Buying a block of seats, one invoice One subscription per learner, bought by them

None of that stops you teaching with it. It does mean the class layer — who is in the group, who has done what, what is due on Friday — stays in whatever you already use, and the platform is the workshop.

How to think about it

Treat the Lab as the practical half of a course you own:

  • The platform supplies the content, the machine-graded practice, the 3D twin, the calibration and vision tooling, and the certificate.
  • You supply the roster, the pacing, the assessment record, the group work, and everything about the physical room.

Teachers who have run it successfully do one thing consistently: they treat each learner's dashboard percentage and module ticks as the progress source, and ask learners to show it at the start of a session rather than trying to administer it from outside. There is no way to see it remotely.

Where to go next

  1. What you need — accounts, subscriptions, arms per group, the room.
  2. Setting up the room — the checklist for the week before.
  3. Planning the course — the twelve modules mapped onto sessions.
  4. Running a session — shape, rotations, and where learners get stuck.
  5. Assessment — what evidence exists and how to build a mark on it.
  6. Safety — read this one before the arms come out of the box.

This is what exists today

Documentation describes the product as it is. If a class feature you need is missing, say so — hello@robonine.com. It is the kind of thing that gets built when enough institutions ask for it.