Skip to content
MakerBuddy

MakerBuddy for teachers

Teach the idea—not the wiring problem.

Lead practical IoT lessons with dependable hardware, visible cause and effect, assessable project work and a path from no-code logic to Arduino.

PlanningClassroom ready
ProgressionLogic to code
SupportBuilt for educators
A school teacher preparing a MakerBuddy IoT Kit lesson with the web dashboard
01

A better first fifteen minutes

Start with a question, not a tangle of jumper wires. MakerBuddy lets students see an input change, control an output and explain cause and effect before the lesson moves into abstraction.

Demonstrate instantly

Put live data on a shared screen, change the environment and ask the class to predict the response.

Differentiate on one device

Beginners use the dashboard and rule engine. Confident learners inspect messages, modify firmware or build their own interface.

Assess real decisions

Ask learners to justify a threshold, explain a failed test and show how evidence changed their design—not simply copy a finished circuit.

02

Your reusable lesson rhythm

  1. 1Hook: Introduce a real problem such as wasted energy or an unhealthy plant.
  2. 2Predict: Ask what the sensor should report and what could affect it.
  3. 3Observe: Read live data and identify a useful input.
  4. 4Control: Operate an LED, servo, buzzer, relay or display.
  5. 5Automate: Express the solution as a condition and action.
  6. 6Challenge: Change a constraint, add a second input or move into code.
  7. 7Reflect: Explain what the system senses, decides and does.
03

Built-in differentiation

Support

Provide a known sensor-to-output example, a target threshold and a checklist. Students can succeed without beginning from a blank page.

Core

Give teams a real-world brief and success criteria. They choose the rule, test the behavior and record evidence.

Stretch

Require multiple conditions, edge-case testing, API use, source-code changes or a custom interface.

04

Assessment prompts that reveal understanding

  • What does your system sense, decide and do?
  • Why did you choose this threshold or timing value?
  • Which test failed, and what did that teach you?
  • What happens at the edge of the sensor range?
  • How would you make this prototype safer or more reliable?
  • What data should remain local, and why?
05

A 32-week path—or one useful lesson

Follow the curriculum from physical computing fundamentals through sensing, automation and capstone projects. Or use a single project idea for a science investigation, computing lesson, club session or design challenge.

Prepare

Review the lesson goal, verify kit contents and test one complete example before class.

Teach

Use the dashboard for a visible shared explanation, then move quickly into paired or small-team exploration.

06

Plan with confidence

MakerBuddy is designed to reduce avoidable setup friction, but practical lessons still benefit from a tested network, charged student devices, clear component routines and a backup demonstration. Start with one reliable build, then let learners change one variable at a time.

Ready for your next lesson

Turn one real-world problem into a memorable class.

Use the prepared learning path or adapt a project challenge for your subject, students and available time.