Whole-class teaching stays front and centre
The middle of the learner workspace becomes a strong lesson stage while notes, learner actions, and progress stay in place around it.
ClassPilot is designed as a build, run, and classroom experience system for computing. The teacher leads the room, the learner stays inside one stable workspace, and the centre of that workspace can become a slide deck, a video, a matching task, a logic builder, a written response, or a support step without throwing everyone into a new interface.
Top actions, right-side support, and bottom progress stay familiar while the centre activity changes.
Release, regroup, reteach, and support happen inside one coherent lesson flow rather than across separate tools.
Presentation, media, matching, sorting, logic, writing, and more can live inside the same classroom shell.
Less reorientation. Fewer repeated instructions. Better visibility while circulating and supporting learners.
Create lessons as a sequence of teacher-led segments and interaction types rather than a pile of disconnected assets.
Teach from one runtime that controls release, timing, support, and what the room sees next.
Give learners one recognisable shell where they always know what matters now and what comes next.
The middle of the learner workspace becomes a strong lesson stage while notes, learner actions, and progress stay in place around it.
The product direction is bigger than slides, bigger than worksheets, and bigger than a task player. ClassPilot is becoming a system for building a lesson, running it live with teacher control, and giving learners a stable classroom experience all the way through.
Structure explanation, interaction, support, and challenge as deliberate parts of one sequence rather than separate destinations.
Hold, release, reteach, and support the class from a coherent delivery model that respects how live classrooms actually move.
The shell stays steady while the central mode changes, so attention can stay on computing rather than on interface reorientation.
Presentation, video, matching, logic, writing, support, and future modes like coding, trace tables, and diagram labelling can all sit in the same lesson frame.
The design assumes a teacher is actively leading, circulating, and shaping the room — not just assigning tasks and stepping away.
Readiness, “I’m stuck”, and teacher-help flows belong inside the product story because they are part of how real lessons succeed.
Calm contrast, bounded panels, and clear hierarchy are intentional: the software should feel composed in a busy room, not gimmicky.
A computing lesson should be able to teach, demonstrate, check, practise, support, and capture evidence without forcing learners through a parade of unrelated tools.
Launch the room into one shared lesson stage where explanation, worked examples, and key instructions are obvious and easy to follow.
Move from presentation to interaction or from media to written response while keeping the surrounding shell stable and recognisable.
Help requests, stuck states, notes, and next-step guidance stay anchored in context instead of splitting off into side systems.
Less repeated setup talk. Better room awareness. A more consistent teaching rhythm across different classes and activities.
A familiar shell that reduces uncertainty, keeps progress visible, and makes it easier to stay oriented when the task changes.
A more coherent model for digital lesson delivery in computing, with evidence capture and support built into the flow.
Join the list for meaningful updates, sharper demos, and early invitations when there is something worth showing to teachers and departments. This is not for noisy drip-fed marketing. It is for people who care about how live computing lessons actually run.
Name and email only.