A build-and-drive railway sandbox that puts kids in the maker's seat: plan a route, cross the land, run the train, iterate.
The tools a child actually touches — and the thinking each one grows.
TrainO drops children onto a freshly generated voxel island with forests, lakes, and snow-capped mountains. They switch to Build mode to design their own railway, then to Drive mode to run a real train along it. A simple cargo economy — farms, mines, a factory, and coins — turns building into a small system to manage. There are no timers and no fail states; every mistake is reversible.
Because TrainO spans K–5, both CSTA levels are listed. Every row ties to a real in-game action — nothing aspirational.
| Code | Standard | How TrainO addresses it |
|---|---|---|
| 1A-AP-08 | Model daily processes by creating and following algorithms (sets of step-by-step instructions) to complete tasks. | Laying track is an ordered sequence of points; the train then follows that algorithm from station to station. |
| 1A-AP-10 | Develop programs with sequences and simple loops, to express ideas or address a problem. | Points are placed in sequence, and the "Loop the Loop" mission has children close the track into a repeating loop the train circles. |
| 1A-AP-11 | Decompose (break down) the steps needed to solve a problem into a precise sequence of instructions. | Connecting two towns forces the child to break the journey into an exact, point-by-point path across the terrain. |
| 1A-AP-12 | Develop plans that describe a program's sequence of events, goals, and expected outcomes. | The Missions panel names a goal and its reward up front; children plan a route to reach it and predict the result (e.g., a city growing). |
| 1A-AP-14 | Debug (identify and fix) errors in an algorithm or program that includes sequences and simple loops. | When a line doesn't connect or a loop won't close, kids use Undo and Remove to find and fix the broken step. |
| 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. | Choosing the right train for the job (the slow Cargo train pays more per delivery) and toggling accessibility settings like Read-Aloud shows tools serve different needs. |
| Code | Standard | How TrainO addresses it |
|---|---|---|
| 1B-AP-08 | Compare and refine multiple algorithms for the same task and determine which is the most appropriate. | Facing a mountain, kids weigh going over (climb) vs. through (tunnel) and pick the better route — then refine it. |
| 1B-AP-11 | Decompose (break down) problems into smaller, manageable subproblems to facilitate the program development process. | The supply chain splits into sub-tasks: build the line, load crops at the farm, drive the route, deliver to the city. |
| 1B-AP-12 | Modify, remix, or incorporate portions of an existing program into one's own work, to develop something new or add more advanced features. | A Share code loads a classmate's island; children ride it and build new track onto it — a literal remix. |
| 1B-AP-13 | Use an iterative process to plan the development of a program by including others' perspectives and considering user preferences. | Build mode is additive; kids revise their railway across sessions, and gallery-walk feedback feeds the next iteration. |
| 1B-AP-15 | Test and debug (identify and fix errors) a program or algorithm to ensure it runs as intended. | Switching to Drive mode tests the design; if the train stalls or the route is wrong, Undo/Remove fix it. |
| 1B-AP-17 | Describe choices made during program development using code comments, presentations, and demonstrations. | Photo and Share give the work an audience; children present and explain their design decisions in a gallery walk. |
TrainO's terrain-crossing choices are engineering problems, so it also supports the Next Generation Science Standards Engineering Design performance expectations:
| Code | Performance expectation | How TrainO addresses it |
|---|---|---|
| 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. | "How do we get the train across the lake / over the mountain?" defines the design problem before a single track is placed. |
| K-2-ETS1-3 | Analyze data from tests of two objects designed to solve the same problem to compare the strengths and weaknesses of how each performs. | Kids run a short train and a long one on the same line and observe which accelerates and tops out better. |
| 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. | Bridge, tunnel, or viaduct? Children generate route options and compare them against the terrain and their goal. |
| 3-5-ETS1-3 | Plan and carry out fair tests in which variables are controlled and failure points are considered to identify aspects of a model or prototype that can be improved. | Change only the train's car count, keep the track the same, and measure top speed — a controlled fair test of one variable. |
Each runs ~20–30 minutes and needs only a tablet, Chromebook, or laptop per child or pair.
Students place track points in order to build a working line between two spots and drive a train along it.
Students identify a terrain obstacle, generate two ways past it (over vs. through / bridge vs. reroute), and justify their choice.
Students build a farm-to-city supply line, break the delivery into sub-tasks, then run a fair test of how train length affects speed.
Open-ended prompts that get kids to explain their design thinking.
A simple 3-level guide for a make-your-own-island project where a child connects at least two places and explains their choices.
| What we look for | 🌱 Getting started | 🚂 On track | 🌟 Full speed |
|---|---|---|---|
| Planning & sequencing | Places a few track points; the line may not connect two stops. | Builds a complete line, in order, between two stations that a train can run. | Plans the route first (sketch or out loud) and builds a connected network of 2+ lines. |
| Solving terrain | Sticks to flat ground and avoids obstacles. | Crosses at least one obstacle with a bridge, tunnel, or climb. | Chooses over vs. through on purpose and can explain the trade-off. |
| Testing & fixing | Rarely tests; leaves errors in place. | Drives to test and uses Undo/Remove to fix at least one problem. | Iterates repeatedly — tests, spots a failure point, and improves the design. |
| Explaining choices | Describes what they built with a few words. | Explains one decision and why they made it. | Presents the railway (Photo/Share) and justifies several design choices. |