Matariki: Animation & Sound
Programming with micro:bit MakeCode
Platform
Digital Technologies Progress Outcomes
Assembling sequences of code blocks to produce specific outputs
Understanding a programmable digital system
Identifying and correcting errors; simple debugging
Understanding that changing values changes outputs and outcomes
Considering how the program components work together
[DDDO] = PO1
Using digital tools to create a purposeful multimedia outcome
Making design decisions and intentional creative choices
Recognising that the finished program produces a real, shareable outcome
Cross-Curricular Links
Social Sciences / Aotearoa NZ Histories
Exploring the cultural significance of Matariki and engaging with the Māori New Year
A musical thinking exercise to reproduce a tune; a constrained but creative visual design challenge to produce a shining star and scrolling text display
Year Levels
Y3-4 (Guided, carefully scaffolded, focus on LED animation and scrolling text with melody as optional extension)
Y5-6 (Guided, with lighter support)
Y7+ (Independent, optional extension opportunities)
Duration
1+ lessons
Achievable within a single session, but consider allowing for two, especially for first encounters with micro:bit or to for extension opportunities
Resources
Differentiation
Consider using the MakeCode simulator rather than the physical micro:bit device, either as a practise tool in a digital context ahead of setting up the hardware, or especially if getting, setting up, or using micro:bit hardware is too challenging or impractical in your learning environment.
Extension
Expand the musical challegne to experiment with programming other familiar melodies, or challenge learners to compose their own.
Prompt learners to apply the principles from this activity to program other shapes, letters, and sounds that celebrate Matariki, te tau hou Māori.
About Activity
This session introduces ākonga to the micro:bit hardware and MakeCode development platfrom by guiding them to create a multimedia animation in celebration of Matariki.
Use code to combine lights and sounds to program an animation that includes a shining star, banner letters, and a familiar melody. Mānawatia a Matariki!
The MakeCode simulator provides a full and effective alternative to physical hardware, which make it an excellent option in settings where hardware availability or other considerations are a constraint.
Teachers should consider:
Hardware Preparation as a pre-lesson task.
Group Assignments and logistics, including student collaboration and content focus.
Digital Safety & Wellbeing to make sure device and other hardware use is safe, supervised, and purposeful throughout. This activity uses MakeCode, a browser-based block coding platform developed by Microsoft, and the micro:bit device. Here are some things to keep in mind:
Familiarise yourself with the MakeCode platform before the lesson at makecode.microbit.org, and make sure MakeCode is accessible on your school devices.
If you’re using physical micro:bit hardware, then test USB connections before the lesson as some managed school devices restrict USB peripherals.
If you’re using the MakeCode micro:bit simulator, then familiarise yourself with the platform before the lesson at makecode.microbit.org/device/simulator.
MakeCode does not require ākonga to create an account to use the simulator or build programs. A Microsoft account is only required to save or share their projects online. Consider whether this is appropriate for your context and how to manage the security of student data.
micro:bits are small, robust devices but should still be handled with care, particularly when connecting and disconnecting USB cables.
Supervise device and hardware use throughout the activity, particularly for younger learners navigating the tools for the first time.
Lesson Progression Guide
This activity can be completed in two ways, either using the physical micro:bit device or using the MakeCode online simulator. Both produce a fully functional Matariki animation program. The key differences are in setup requirements, classroom logistics, and the experience of seeing the program run on real hardware. Here are some features of each option to help you choose the approach that suits your context.
Hardware Pathway (micro:bit with MakeCode)
Requires one micro:bit and one USB cable per learner or pair, and a laptop or Chromebook with a USB port.
Introduce the micro:bit as a small, programmable computer; show ākonga the LED matrix, buttons, and USB connector.
Open MakeCode, and model the interface, like the on start block, the block palette, and the simulator panel.
Model adding a show LEDs block and designing a star pattern on the 5×5 LED grid, then flash to the device and show the result on the physical hardware.
Support ākonga to design their own star animation and flash their program to the device.
Begin adding a scroll string block for the Matariki banner, and test it on the device
Add a play melody block, and select a familiar tune to test on the device. Hearing the melody play through the micro:bit speaker is a worthwhile experience.
Complete and debug the full program sequence.
Extension — experiment with other shapes, letters, sounds, or compose an original melody using individual note blocks.
Share finished micro:bits — pass them around the class, display them, or connect to a speaker for effect.
Reflect — what does it feel like to hold a device that runs a program you wrote?
Software Pathway (MakeCode micro:bit Simulator)
Require a laptop, Chromebook, or other device with a browser and internet access. Suited where micro:bit hardware is unavailable, where USB access is restricted on school devices, or where kaiako prefer a lower-logistics first encounter with MakeCode.
Navigate to makecode.microbit.org/device/simulator on a school device and make sure it loads correctly. No account is needed to build and test a program in the simulator.
Open a new project and confirm the simulator panel is visible, where ākonga will see their program running in real time as they build.
Introduce MakeCode, what it is, how the block palette works, and how the simulator shows the program running live as blocks are added.
Model adding a show LEDs block, designing a star on the 5×5 grid, and watching it appear on the simulator with immediate visual feedback.
Support ākonga to build their own star animation and experiment with the LED grid design.
Add a scroll string block for the Matariki banner, and watch it scroll across the simulated display.
Add a play melody block, and listen to the melody through the computer speakers via the simulator's audio output.
Test and debug the full sequence in the simulator, and adjust until the animation, text, and melody play in the right order.
Extension — try other shapes, letters, a different melody, or compose an original melody using individual note and duration blocks.
Share finished programs — connect to a projector or screen, where each learner or pair can run their simulator and show the class their Matariki animation.
Reflect — what was it like working with a virtual micro:bit? What might be some advantages of testing in a simulator before flashing to hardware?
