Loading activity… Taking a little longer than usual…

pkrp-about

This activity invites ākonga to use ScratchJr to build a simple interactive glossary program that teaches everyday kupu in te reo Māori and English. Rather than just labelling a picture, learners bring each word to life with their own voice and their own choice of image, turning a vocabulary exercise into something creative they can share.

Learners will choose a backdrop and a sprite to represent an object, then record themselves saying its name in both languages before adding the written words and tying it all together so the sprite plays the sound and shows the text. They’ll finish by testing their app and working together to fix any issues that come up. Ka pai te mahi!

pkrp-dt-detail

ctdt-po2

  • Sequencing code blocks to build a working program with a clear purpose

  • Testing and debugging when an element doesn’t work as expected

dddo-po1

  • Following guided steps to manipulate images, recorded audio, and text within ScratchJr to build a digital outcome

  • Using device features to create original content for an original program

dddo-po2

  • Selecting a backdrop, sprite, and recording that best communicate meaning to a real end-user

  • Making decisions about how spelling and pronunciation should be presented to a real end-user

pkrp-cc-detail

learning-languages

See ‘Te Reo Māori’ link below.

te-reo-maori

Everyday vocabulary, understanding and producing familiar te reo Māori and English words for objects in their environment.

pkrp-diff

  • Simplify the word list by pre-selecting three or four familiar kupu, so learners spend their attention on the ScratchJr blocks rather than choosing vocabulary.

  • Stretch confident ākonga by having them record both a slow, clear pronunciation and a natural-speed one, to notice the difference.

  • Pair up less confident readers with a buddy for the Say-block typing step, so text entry doesn’t become a barrier to finishing.

pkrp-ext

  • Add extra scenes to turn the single sprite into a small collection, building a mini glossary of several kupu instead of one.

  • Swap the theme by choosing sprites from a different category, like animals, kai, or whānau, to make a themed kupu app for a specific topic the class is studying.

pkrp-notes

Teachers should consider:

  • Device access & setup, including checking that tablets are charged, that ScratchJr is installed and up to date, that each device’s microphone and camera permissions are enabled, and that each device has enough storage for saved projects and recorded sound files.

  • Group size and pairing, deciding whether ākonga work individually, in pairs, or in groups, including supporting collaboration, content focus, and technical experience.

  • Sound recording location, including planning where ākonga can record to avoid overlapping background noise and disrupting others.

  • A prepared kupu list, including considering choosing or confirming ahead of time the words ākonga will use and referencing resources like Te Aka Māori Dictionary and Paekupu in advance.

  • Te reo Māori pronunciation support, including having a fluent speaker, audio reference, or other reliable modelling available before ākonga record.

pkrp-dsw

ScratchJr is a free, closed, tablet-based app with no login or account required, no ads or in-app purchases, no internet browsing, and it doesn’t collect information that identifies a child by name, making it a lower-risk digital tool. ScratchJr works fully offline once installed, with all projects and files saving locally to the device they are created on. Even so, always take steps to make sure device use is safe, supervised, and purposeful throughout.

  • Before the activity

    • Make sure the ScratchJr app is up to date.

    • Consider turning off internet access on tablets since ScratchJr doesn’t need it to run.

    • Remind ākonga to handle tablets with care and to consider what is appropriate language or other sounds to include in their project during recording and programming.

    • Remind ākonga of your school’s digital use agreement before beginning any lesson that involves digital devices, digital platforms, or the internet.

  • During the activity

    • Set clear expectations around safe and purposeful device use at the start of each lesson.

    • Supervise and actively support device use throughout.

    • Discuss openly what is and isn’t appropriate to include in a ScratchJr project, as well as support ākonga to re-record a take rather than feel stuck with it.

    • Support ākonga to know that if they encounter content that feels inappropriate, confusing, or upsetting that they can flag this with kaiako without concern.

  • After the activity

    • Since finished storybooks and voice recordings stay on the device, agree how they’ll be identified and shared later.

    • If tablets are shared with other classes, agree who’s responsible for keeping track of or clearing projects and sound files, so no one’s stuff gets lost, mishandled, or deleted by accident.

pkrp-lp

>>> y0-3 | Y0-3 | 1 Lesson (Guided)

A teacher-led walkthrough works best here, where you model each ScratchJr step on a shared screen before ākonga try it themselves.

  • Explore & Choose — Guide ākonga to pick a backdrop and one sprite to represent a kupu the class has already learned together.

  • Record & Build — Support ākonga to record their pronunciation and add the Start on Tap, Sound, and Say blocks step by step, checking in after each block is added.

  • Test, Debug & Share — Have each learner press Green Flag to test their app, and help them fix issues, like any missing blocks or blocks that are out of order. Then share finished apps as a class.

>>> y4-6 | Y4-6 | 1 Lesson (Guided to Independent)

Ākonga can work through the guide with less step-by-step support, checking in with a partner rather than the teacher at each stage.

  • Plan & Build — Direct ākonga to select their own kupu, backdrop, and sprite, then independently work through backdrop, sprite, action, and recording steps.

  • Add Vocabulary — Have ākonga use a prepared resource to confirm spelling before typing both languages into their Say blocks.

  • Test, Debug & Share — Ask ākonga to test their app, debug any issues themselves first, then share their finished app with a partner to try.