01 · EXPLORE
Start with what the interaction could sense and do
Choose an input and an output. Think about the physical action you want the prototype to detect and the response it could produce. These choices establish the starting point for your interaction.
02 · DEFINE
Use IPO to describe the interaction
Define your interaction as Input → Process → Output. Input is what the prototype senses. Process describes the rule or behaviour between the input and response. Output is what the prototype does.
Processes include patterns such as Trigger, Toggle, Threshold, Delay, Sequence and Repeat. You do not need to memorise these. Use the Pattern Library to understand them when they become useful.
03 · MAKE
Implement the interaction in MakeCode
This companion does not replace MakeCode. Use the interaction logic and block reference as a starting point, then open MakeCode to build and modify the program for your Circuit Playground.
Record what you changed and what you found difficult in Field Notes. Keep the implementation connected to the interaction you are trying to create.
04 · TEST
Watch another person use the prototype
Ask someone else to interact with your prototype while you observe. Record what you expected, what actually happened, what they did and what surprised you. Testing is about learning from the interaction, not proving that the prototype is correct.
05 · REFLECT
Record what the prototype taught you
Capture discoveries, changes in your thinking, what matters most and what you are struggling with. A working prototype is evidence for design thinking, not simply a technical achievement.
06 · REPORTS
Save meaningful checkpoints
Create a report snapshot when you reach a useful point in the project. Snapshots are retained in the project history and can be exported individually or together.
SENSE · PROCESS · RESPOND
Use the Pattern Library when you need more context
The Pattern Library explains interaction inputs, process patterns and outputs in more detail. It also points to external references for Circuit Playground and, when useful, other platforms such as Arduino, ESP32 and Raspberry Pi Pico.
The concepts transfer between platforms even when their implementation changes.
IMPORTANT
Your project is stored locally
This tool uses browser localStorage. Browser data can be cleared or lost, so save and export your project regularly. Create a report snapshot before seeking support and export it when sharing your work.
COMPLEXITY CEILING
Know when to stop and ask for help
This companion intentionally supports only a small interaction chain. If you need more inputs, outputs, conditions or stages, the interaction is becoming complex.
Pause, create a support snapshot and speak with your tutor or technical staff before continuing in MakeCode.