🕹️ Self-paced family project · 6 missions
Bounce Lab: Build a Web Game
Make a small browser platformer your family can explain: collect three stars, reach gold, tune one rule and add a middle-platform checkpoint.
No installation, payment, child account, or AI key to begin in the browser. Later authored missions use guardian access. Full project extensions may need additional tools.
What you will make
Original Bounce Lab starter inspired by BOUNCR
- Explain input, state, rules, and drawing.
- Tune one rule using evidence.
- Implement checkpoint recovery.
- Show a complete game and test record.
Settle in together
Laptop or desktop with a modern browser for editing. Phones can read the guide and observe or try the preview. Start with fictional data.
Allow about 5 minutes to get ready. Six missions in order. Try one or two 5–12 minute activities, take a break, and resume at the next activity. Plan several short sittings per mission; the full 75–90 minute lesson remains the detailed reference. End each sitting with a saved copy and one sentence: next time we will… Times are estimates awaiting family pilots.
- For ages 9–12, work beside a parent on a computer with a keyboard. A phone can read the guide and watch; use a computer for editing. Older learners may try the full lesson's stretch task after the core checks.
- Open the first mission's browser workspace and press Run before installing anything. No payment, child account, or AI key is needed for that introduction. If the runtime reports unavailable, keep your files, read its error, and use the course-specific fallback below with adult help.
- Before ANY local trace, model test or build, use this course’s full reference handoff: Save and Export backup, retain the JSON backup, extract the matching ZIP into a new folder, copy every current source file with transfer-workspace.mjs, and run verify-workspace.mjs with your actual edited value from that extracted folder. JSON is a source backup, not an executable ZIP; Import backup does not update disk files. Keep results beside the exact source version tested. If you skip transfer, label downloaded checks baseline-only.
- The baseline has two jumps and three platforms. It recovers at start after falling and keeps stars; the middle checkpoint is a later feature, not already implemented.
- Download fallback: /lab-starters/arcade-games.zip. In its folder a parent runs python3 -m http.server 8080 --bind 127.0.0.1 and opens http://localhost:8080. Keep the server open; double-clicking a module page is unsupported. With Node prepared, npm test runs rule checks without npm install.
- model.js holds RULES, PLATFORMS and state; main.js handles controls and Canvas; index.html holds instructions. Full lesson code supplies the exact checkpoint landing and falling replacements.
- Keep the original starter unchanged as a reference. Export a working copy before a risky edit or reset. Work and the optional progress checklist stay on this device; an export is your portable backup. A checked box records your own report, not a verified assessment.
- Use invented names, notes and records. The parent handles accounts, optional AI and sharing. Predict together, let the child make one choice, change one thing, test it, then explain what happened. An assistant is optional; the supplied code and a partner work too.
Two people, different jobs
- Child · driver & designer
- Write the player promise, choose the edit, compare attempts and explain what survives a fall versus Restart.
- Parent · thinking partner
- Help start the preview, keep before copies and read test errors. Ask the child which player need each change serves.
A path you can pause
These are complete missions, not one-sitting deadlines. Each family guide breaks the work into small activities. Return to the last activity you chose to remember.
MISSION 1 · PUBLIC FIRST MISSION
Choose the player and make the first bounce
Run Bounce Lab and turn a game idea into a testable promise.
Full mission plan: 90 minutes · split across activities
MISSION 2 · GUARDIAN ACCESS
Make the rules predictable
Trace and tune one movement rule using a repeatable experiment.
Full mission plan: 90 minutes · split across activities
MISSION 3 · GUARDIAN ACCESS
Design controls for real players
Improve control instructions and compare keyboard with buttons.
Full mission plan: 90 minutes · split across activities
MISSION 4 · GUARDIAN ACCESS
Add a checkpoint that helps players recover
Implement one complete middle-platform checkpoint feature.
Full mission plan: 90 minutes · split across activities
MISSION 5 · GUARDIAN ACCESS
Become a failure detective
Find a reproducible mismatch, fix it, and repeat the evidence.
Full mission plan: 90 minutes · split across activities
MISSION 6 · GUARDIAN ACCESS
Open your mini arcade
Demonstrate a working loop and defend one design decision.
Full mission plan: 90 minutes · split across activities
Leave a trail for next time
The optional mission checklist remembers your place in this browser. Workspace files have their own save controls; export them for a portable backup. Write down one change, one test observation, and the activity you want to try next.
Download the original starter for the full local project ↓About this family pilot
Authored from family project evidence with an original teaching starter. Classroom timing and the actual learner devices need a facilitator rehearsal; this draft is not classroom validated.
Complete course plan · extended setup, camp & project evidence
Begin in the browser workspace with no installation. The original tools and prerequisites below apply to the full downloaded project and its extensions. Native mobile tools and physical hardware are separate adult-prepared steps. Portfolio themes describe your project; no credential is automatically awarded.
Create a browser platformer, tune movement, add a checkpoint, and use playtests to defend your design.
Full course platforms: Web browser · Keyboard and touch · Ages 9-10, 11-13, 14-16
Your project
Original Bounce Lab starter inspired by BOUNCR
- Explain input, state, rules, and drawing.
- Tune one rule using evidence.
- Implement checkpoint recovery.
- Show a complete game and test record.
Before you begin
- Comfort editing a number or short line.
- An adult can prepare a local static server and optional Node test runtime.
Materials
- Computer and keyboard
- Paper for brief and tests
- Optional touch device
Your tools
- Bounce Lab starter
- Complete original browser game with no account or package dependencies.
- Download /lab-starters/arcade-games.zip and follow README.md.
- Browser, editor, Python or static server
- Edit and preview local JavaScript modules.
- Run python3 -m http.server 8080 --bind 127.0.0.1 in the unzipped folder.
- Node model checks
- Repeat rule and route checks without drawing.
- With Node installed run npm test; npm install is not required.
Learn online
Six weekly 90-minute sessions: 10 minutes to predict, 15 to explain, 40 to build, 15 to test, and 10 to reflect.
Plan around 90 minutes per session; pause and revisit at your own pace.
Adult support: A facilitator prepares tools and operates AI through JR Playground or an adult-managed assistant. Learners make choices, edit, and verify; no personal AI account is required.
Build at camp
Five days with 180 planned minutes per day, including project work and group activities. The course outline does not reserve a camp place.
Day 1: Day 1 — Brief and working model
- Complete the first two lessons in paired studios.
- Alternate driver and navigator and take a movement break between studios.
Day 2: Day 2 — Controls
- Rotate through keyboard and touch stations and record misunderstandings without coaching.
- Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
Day 3: Day 3 — One meaningful feature
- Partners try to break written recovery rules by falling at different moments.
- Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
Day 4: Day 4 — Failure detectives
- Award bug-hunt points for clear reproduction notes, not the number of complaints.
- Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
Day 5: Day 5 — Future Architects showcase
- Host an arcade gallery where visitors leave one observation and one question.
- Use remaining studio time for rehearsal, peer feedback, breaks, and individual practice.
Facilitator preparation
- The same six outcomes apply online and at camp; additional camp studio time supplies practice, not extra required content.
- Choose guided, independent, or stretch tasks by confidence. Ages 9–10 often pair with an adult; ages 11–13 own bounded changes; ages 14–16 can justify and test architecture choices.
- Prepare starters before class. Keep family repositories and personal data out of student workspaces.
Show what you built
Deliver a small playable game for a chosen player, demonstrate a tested improvement, and explain its input, state, rules, output, and one design tradeoff.
- Purpose
- A brief names the player, loop, finish, and one idea left for later.
- Working system
- A fresh run reaches the intended finish; recovery and restart match the specification.
- Evidence
- A record contains normal, boundary, failure, and repeated-after-fix checks with device details.
- Architect explanation
- The learner explains a changed rule, a tradeoff, and how an AI suggestion was checked.
Portfolio theme: Arcade Architect
Use the rubric with a guardian or mentor and record your evidence in your builder notebook.
Build with care
- Use fictional player names and original shapes; no child photos, contacts, passwords, or API keys belong in the starter.
- An adult operates external AI and manages any public sharing; verify each suggested change with a prediction and check.
- Take movement breaks and offer partner-operated controls when needed.
Inspired by our projects
- BOUNCR web
- Canvas game loop, jump physics, checkpoint recovery, collectible stars, and data-driven levels.