ScratchJr shines when the first projects are tiny victories. A child who makes a character move and say hello has already done something real. A child who is told to “build a game” on day one often hands the tablet back. Keep the runway short, the cheering specific, and your hands off the blocks unless they ask.
This guide is for parents and caregivers helping kids roughly ages five to seven (and curious older beginners). You will get project recipes, scripts, age notes, and habits that keep the child as the programmer—not the adult secretly driving.
What ScratchJr is good for
ScratchJr is a block-based app where kids snap pictorial coding blocks to make characters move, speak, and interact on a stage. It is gentler than full Scratch: fewer blocks, bigger targets, no typing required.
It is ideal for:
- First experiences with “program then run”
- Visual stories and mini animations
- Practicing sequence and simple triggers
It is not ideal as endless unsupervised entertainment. Treat it like art supplies with a timer.
Specific praise teaches them what to repeat: “You made it move and talk,” not only “Good job.”
Co-regulation still applies at the tablet
Frustration is part of debugging. When shoulders rise, shrink the goal before you take over. A calm “Let’s try one block” beats a tense “Just let me fix it.” Your nervous system teaches as much as the app.
Before the first project
- Install ScratchJr together.
- Open a blank project and name it something silly.
- Show the green flag / start idea in kid language: “This starts your plan.”
- Agree on a time box (ten to fifteen minutes).
- Decide who holds the tablet—usually the child, with you beside them.
If they want you to “just do it,” offer choices instead of taking over: “Should the cat move or hop first?”
Setup script
“We’ll make something tiny today. When the timer rings, we save and show Bear. You tap. I help with ideas if you ask.”
Project 1: The hello wave
Goal: One character appears, moves a little, and says hello.
Steps
- Add a character you both like.
- Add a motion block (move right or hop).
- Add a “say” block with a short hello.
- Trigger start and watch.
- Celebrate like it is opening night.
Scripts for parents
- “You made the stage do something on purpose.”
- “What should it say next time?”
- “Want to change the move or the words?”
What to avoid
Do not stack eight blocks on day one. Two or three blocks that work beat a tower that confuses everyone.
Worked example
Character: fox. Blocks: hop, say “Hi.” Run. Child laughs. You say, “You made a plan and the fox followed it.” Stop there even if they beg for fireworks. Hunger to return is the goal.
Project 2: Cross the stage
Goal: Character starts on one side and travels to the other.
Talk about start position. Drag the character left. Program motion until it reaches the right. If it goes too far, that overshoot is a friendly bug—adjust the number of move steps.
Variation by age
Younger kids use one long move. Older kids chain smaller moves and add a wait so it feels dramatic.
Debugging prompt
“It went too far. Should we use fewer hops or start closer to the edge?”
Let them pick. Ownership of the fix matters more than the perfect path.
Project 3: Two characters talk
Goal: A tiny conversation.
Add a second character. Give each a say block. Use wait blocks so they take turns instead of talking over each other. This introduces timing—an early form of coordination between parts of a program.
Debugging prompt
“They’re both talking at once. Which wait should we add?”
Let them try the wrong wait first. Seeing the overlap teaches more than your lecture.
Script for turn-taking pride
“You taught them to take turns. That’s timing—real programming thinking.”
Project 4: Speed race (still tiny)
Goal: Two characters move; one arrives first because its motion blocks differ.
Keep it cooperative: “Can we make the turtle surprise-win?” Changing values and re-running is experimental thinking. Avoid turning it into sibling humiliation.
Soft competition script
“This is a science race, not a who-is-smarter race. We’re testing which blocks are faster.”
Project 5: Mini story in three scenes
ScratchJr supports multiple pages. Make three pages: beginning, middle, end. Example: character at home → walking → at park saying “We made it!”
This mirrors comic-panel sequencing kids may already know offline. Connecting offline comics to ScratchJr pages makes the tool feel less alien.
Offline bridge
Draw three panels on paper first. Then rebuild the same sequence in ScratchJr. The paper draft reduces overwhelm when the app feels busy.
Project 6: Button-triggered surprise
Use a trigger so tapping a character starts a funny hop or sound. Kids love cause and effect they can poke. Keep sounds gentle if sensory sensitivity is in the house.
Sensory note
Preview volume together. One gentle sound beats a startling blast that ends the session in tears.
Project 7: Hide and appear (optional stretch)
Once Projects 1–3 feel easy, try a simple hide/show or size change for a “magic” moment. Keep it one new idea per session. Stacking every block category in one sitting creates fog, not mastery.
How to coach without hijacking
Sit on your hands if you must. When they are stuck:
- Ask what they want to happen
- Ask which block might be closest
- Suggest trying one change
- Run it
- Notice together
Grabbing the tablet to “fix it real quick” teaches them their ideas need an adult patch. Slow help builds ownership.
Scripts when they want to quit
- “Let’s save this and make a brand-new tiny thing.”
- “Want the character to only move—no talking today?”
- “Should I be the idea person while you tap the blocks?”
- “One more try, then we show Bear—even if it’s silly.”
Shrinking the goal restores agency.
When they beg you to build it
Offer a role split: they choose character and words; you only snap what they point to. Gradually return taps to their fingers. Being the pointer is still programming thinking.
Session structure that prevents meltdowns
- One-minute replay of yesterday’s project
- One new micro-goal
- Save and show a caregiver or stuffed audience
- Stop while they still feel successful
Stopping early is a feature. It leaves a hunger to return.
Timer script
“Ten minutes. When it rings, premiere time—even if we’re mid-idea. We can continue next session.”
Age and readiness notes
Ages 5–6: Need help finding blocks; thrive on Projects 1–3.
Ages 7–8: Can attempt multi-page stories and simple races.
Older beginners: Still start tiny. Pride comes from polish, not from skipping the basics.
If reading is early, rely on icons and your narration. ScratchJr was built for that.
Readiness signs (and not-yet signs)
Ready-enough: curiosity about making something move, willingness to try again after a wrong run. Not-yet: only wants to watch YouTube builds, melts down at any wait. Honor unplugged coding games for a while, then return.
What to avoid
- Open-ended “make a game” on day one
- Comparing projects to YouTube prodigies
- Ignoring time limits because “they’re learning”
- Fixing bugs so fast they never see the broken run
- Forcing ScratchJr on a child who clearly wants blocks on the floor instead—honor the unplugged preference for a while
- Turning every session into a lecture about careers in tech
Pairing ScratchJr with offline play
On alternate days, play command-card robots or draw paper paths. Then say, “ScratchJr is the same idea with characters.” The bridge reduces fear when a block does something unexpected.
Two-day rhythm
Day A: Unplugged obstacle course for a stuffed animal.
Day B: ScratchJr hello wave or stage cross.
Name the link out loud once. Kids feel smarter when tools rhyme with play they already trust.
A two-week starter plan
Week 1: Hello wave twice; cross the stage once. Same character if they want familiarity.
Week 2: Two-character talk; optional third page story if joy is high. Save everything.
Looking back at Project 1 in a month is powerful evidence of growth.
Weeks three and four
Week 3: Replay week-one project; add one wait or one new word. Polish beats brand-new complexity.
Week 4: Stuffed-animal premiere night. Dim lights, run once, clap. Invite a sibling only if kindness can hold.
If a week is missed for illness or travel, restart with hello wave. Tiny restart beats abandoned “we’ll wait until we have time for a big project.”
Common ScratchJr stuck points
“The character won’t move.” Check whether a start/trigger block is connected. Kids often build a beautiful chain that never runs.
“It moves the wrong way.” Celebrate: the program ran—direction is an edit, not a disaster. Flip the motion block and rerun.
“They want YouTube-level games.” Name the gap kindly: “Those took lots of tiny projects first. Today we make one tiny piece.” Show them how professionals also start small.
“Siblings fight over the tablet.” Use a visible timer and a project-each rule. Or one child directs while the other taps—then swap.
“The app feels laggy.” Close other apps. Lag feels like a code bug and creates false debugging. A calmer device keeps the lesson honest.
“They delete everything in frustration.” Teach Save early. Keep a “museum” project they are not allowed to wreck—open a copy for experiments.
Sharing without comparison
Invite a stuffed-animal premiere: dim the lights, run the project once, clap. Family group chats can receive a screenshot—not a demand for relatives to critique. If an older cousin codes too, frame it as “different projects,” not a race.
Classroom or club tip: gallery walks where kids notice one kind thing about someone else’s project beat ranked contests for this age.
Script for kind feedback
“Notice one thing their character does on purpose. That’s it—no scores.”
Accessibility and device notes
Large tablets are easier than tiny phones. If motor control is tricky, let them point while you tap, then gradually hand over control for single blocks. Reduce background apps so ScratchJr does not lag—lag feels like a bug in their code and creates false debugging.
If your child uses hearing or vision supports, preview sound and contrast together. Adjust volume early. Sensory comfort keeps the programmer in charge.
Related reading
For free paths that include unplugged warm-ups, see coding for kids free. Offline practice that transfers well lives in unplugged coding activities for kindergarten and screen-free coding games for kids. When comparing other digital play, read kids programming games.
