Input
A signal the program can read.
Curriculum topic
Input is information entering a system. Output is the visible, audible, or physical action the system produces.
Why it matters
Naming inputs and outputs helps students stop treating devices as magic. A key press is input; a moving sprite is output. A button is input; an LED or buzzer is output. Code connects them.
Real-world connection
A doorbell maps a button press to sound. A keyboard-controlled game and a microcontroller circuit use the same input-process-output structure with different materials.
The connection shows where the idea returns; it does not claim every advanced application is taught in this first topic.
Math and logic kernel
A signal the program can read.
Rules that decide how the signal matters.
An action people or other systems can observe.
The deliberate connection between input and response.
Small examples
Map four keys to coordinate changes.
Produce sound while or after a button is pressed.
Show a measured result.
Change movement after a measurement.
Program connections
Beginner-friendly programming through original games, animations, simulations, and interactive stories.
Commands, sensors, simple electronics, simulations, and physical systems organized around Sense, Decide, Act.
A future bridge from visual programming to Lua, 3D objects, events, and larger game systems.
Common mistakes
The program defines an output but does not check the signal.
Several inputs control the same action without priority.
Code listens to a different input than the build uses.
The user cannot tell whether the input was recognized.
Lesson and projects
Connect a button input to visible and audible outputs, then improve the alarm's state rules.
Open projectDesign a timed traffic-light sequence, then add a pedestrian input or state rule.
Open projectQueue or trigger movement commands for a robot hamster navigating a tiny security map.
Open project