Space Builders — a goal-free Moon-colony sandbox for young builders.
Space Builders is a sandbox: children build a city on the Moon by tapping a picture and then tapping the ground. There is no score, no timer, no way to lose, and nothing locked. Every one of the 41 buildings is available from the first second. The learning happens in what children choose to build, how they arrange it, and how they explain it — not in beating a level.
The game is deliberately built for pre-readers. A friendly narrator says the name out loud of every category and every building the child taps, so a five-year-old who cannot yet read "Greenhouse" still learns the word. All controls are large, touch-first buttons designed for Chromebooks and iPads.
Homes, Power, Plants, Space, Fun, Machines, Science, and Roads. Tapping a tab speaks the category name aloud and shows that group's buildings.
Each card shows a picture and a short name. Tapping a card speaks its name ("Dome House") and picks it up; the child then taps the Moon to place it.
The default mode. Drag to pan across the Moon, pinch or scroll to zoom, and two-finger twist or right-drag to orbit the camera around the colony.
Rotates the held building 90° before it is placed. It lights up only while a building is selected, so children learn it belongs to the act of placing.
Removes a building with a sparkle and a "Bye bye!". Children can also simply tap any placed building in Move mode to see its name and an erase button.
Wipes the whole colony, but only after a second confirming tap — a built-in "are you sure?" that prevents accidental loss of work.
Paths, Tubes, and Train Track can be dragged to paint a whole line at once, instead of tapping each square.
Tubes and Train Track sense their neighbors and reshape themselves — straight runs, corners, T-junctions, and 4-way crossings all join into one continuous network.
Lay Train Track and a train rides whatever line the child builds, pulling into stations and turning corners. A larger loop automatically runs more trains (up to four).
Building homes causes little astronauts to move in and walk around the colony, and a supply pod flies down to deliver them.
Places a garage that sends out a rover, which drives along the Paths and Tubes the child has laid down.
Launches a rocket with a spoken "Three! Two! One! Blast off!" countdown and a glittery trail. It lifts from the child's Rocket Pad if they built one.
Counts everything the child has built. It only ever goes up as they create — it is encouragement, never a score to beat.
Turns the narrator voice and sound effects on or off — essential for a classroom of shared devices or a sound-sensitive learner.
| Code | Performance Expectation | How this game addresses it |
|---|---|---|
| K-ESS3-1 | Use a model to represent the relationship between the needs of different plants or animals (including humans) and the places they live. | The colony is the model. To support space friends, children place Dome Houses (shelter), Air Maker and Air Tank (air), Water Tank (water), and Greenhouse or Veggie Farm (food). Astronauts only move in once homes exist, making the needs-to-place relationship visible. |
| K-2-ETS1-1 | Ask questions, make observations, and gather information about a situation people want to change to define a simple problem that can be solved through the development of a new or improved object or tool. | Children define a real problem before building — "our astronauts can't get from the houses to the lab" — then choose Paths, Tubes, or Train Track to solve it. Lesson 2 runs this cycle explicitly. |
| K-2-ETS1-2 | Develop a simple sketch, drawing, or physical model to illustrate how the shape of an object helps it function as needed to solve a given problem. | Children sketch a colony plan, then build it. Shape genuinely drives function here: Tubes must physically touch to form a connected corridor, and Train Track must form an unbroken line or the train cannot travel it. |
| Code | Standard | How this game addresses it |
|---|---|---|
| 1A-CS-01 | Select and operate appropriate software to perform a variety of tasks, and recognize that users have different needs and preferences for the technology they use. | Children choose the right tool for each task — Move to look, Turn to rotate, Erase to remove. The spoken-name narration and the 🔊 toggle are a concrete, discussable example of software meeting different user needs (a pre-reader vs. a child who needs quiet). |
| 1A-AP-08 | Model daily processes by creating and following algorithms (sets of step-by-step instructions) to complete tasks. | In Lesson 3, children write a numbered "build recipe" and a partner follows it move-for-move in the game. Building is inherently sequential: pick a tab, pick a card, aim, tap. |
| 1A-AP-11 | Decompose (break down) the steps needed to solve a problem into a precise sequence of instructions. | "Build a Moon base" is too big to do at once. Children break it into parts — homes first, then air and water, then the paths that join them — and place each piece in order. |
| 1A-AP-12 | Develop plans that describe a program's sequence of events, goals, and expected outcomes. | The sketch-before-you-build step in every lesson is exactly this plan: what I will build, in what order, and what it should look like when finished. |
| 1A-AP-14 | Debug (identify and fix) errors in an algorithm or program that includes sequences and simple loops. | The game gives honest, immediate feedback for debugging. If Train Track has a gap, the train will not cross it; if a Tube is one square short, the corridor does not join. Children hunt for the break and repair it with Erase and re-placement. |
| 1A-AP-15 | Using correct terminology, describe steps taken and choices made during the iterative process of program development. | The conversation starters in Section 4 ask children to narrate their build using real tool names — "I used Turn so the door faced the Path" — which is precisely this practice. |
Older students can play the same sandbox with a harder brief (a fixed footprint, a required loop, or a partner's blueprint). These codes then apply:
| Code | Standard | How to reach it |
|---|---|---|
| 3-5-ETS1-1 | Define a simple design problem reflecting a need or a want that includes specified criteria for success and constraints on materials, time, or cost. | Give constraints the sandbox does not impose: "exactly 12 buildings, every home reachable by Tube, finished in 20 minutes." |
| 3-5-ETS1-2 | Generate and compare multiple possible solutions to a problem based on how well each is likely to meet the criteria and constraints of the problem. | Two students build competing Train Track layouts for the same stations, then compare which carries trains more directly and uses fewer track pieces. |
| 1B-AP-11 | Decompose (break down) problems into smaller, manageable subproblems to facilitate the program development process. | Students split the colony into zones — housing, power, transit — assign each to a teammate, then merge the results into one base. |
| 1B-AP-15 | Test and debug (identify and fix errors) a program or algorithm to ensure it runs as intended. | Students deliberately build a broken track loop, trade devices, and race to find and repair the other team's gap. |
Standards references: Connecticut State Department of Education · NGSS (nextgenscience.org) · CSTA K–12 CS Standards
Students will identify the basic needs of people and build a Moon colony that provides each need, explaining which building meets which need.
Students will connect separated buildings with a continuous Tube network, then find and repair a deliberate gap — an authentic first experience of debugging.
Students will write a precise, numbered set of build instructions and test it by having a partner follow it exactly, then revise any step that was too vague.
Because there is no score, the thinking lives in the child's explanation. These questions pull it out. Ask them while the colony is on screen so the child can point.
Give students 20–25 minutes to build a colony that (a) meets all four survival needs, (b) connects its buildings with Paths, Tubes, or Train Track, and (c) can be explained out loud in a one-minute tour. Assess by listening to the tour, not by counting buildings.
| Criterion | 1 — Getting Started | 2 — Building It | 3 — Space Architect |
|---|---|---|---|
| Meeting needs K-ESS3-1 |
Places buildings freely; needs are not yet considered. | Provides shelter plus one or two other needs (air, water, or food). | Provides all four needs and names the building that supplies each one. |
| Connecting K-2-ETS1-2 |
Buildings sit apart with no Paths or Tubes between them. | Draws some Paths or Tubes, though parts of the base remain unreachable. | Builds a continuous network reaching every area; corners and junctions join cleanly. |
| Planning & order 1A-AP-11, 1A-AP-12 |
Builds by trial and error with no stated plan. | Describes a rough plan and mostly follows it. | States a plan first, builds in a sensible order, and explains why that order helped. |
| Fixing problems 1A-AP-14 |
Needs adult help to notice something is not working. | Notices a problem, such as a gap, and fixes it with prompting. | Independently spots the break, repairs it with Erase, and explains the fix. |
| Explaining 1A-AP-15 |
Points at buildings; uses few names. | Names most buildings and gives simple reasons for placement. | Gives a clear tour using correct tool and building names, and justifies design choices. |