The Square Canisters Apollo 13 Needed, and What Was at Stake

The tablet hand-back test reveals what is pulling your child back: a prize screen, a score, or a problem they still want to solve. After five minutes, pause the app and ask what they were trying to do when time ended.

In April 1970, Apollo 13 was headed toward the Moon when an oxygen tank exploded. Jim Lovell, Jack Swigert, and Fred Haise had to preserve power, water, and breathable air while Mission Control in Houston worked through problems whose answers were far from certain.

One of those problems was painfully concrete. The lunar module had round carbon-dioxide canisters; the command module had square ones. The crew needed a way to make the square canisters work in the lunar module. NASA’s account of Apollo 13 documents the improvised adapter built from materials already aboard, including plastic bags, cardboard, and tape.

The point was never the pile of materials. It was the unresolved problem. Everyone involved had a reason to keep working because the next action changed what might happen.

What your child reaches for after the pause

A prize screen can create a quick urge to tap again. So can a flashing score, a daily streak, a wheel, or a chest that promises a random reward. Those systems can hold attention, but the hand-back test asks a more useful question: what does your child describe when you take the tablet away?

Listen for the difference.

“I was about to get another prize” tells you the app’s reward system has become the main event.

“I need to fix the train route” or “I want to finish the story” points somewhere else. Your child has a goal inside the activity. The unfinished task has its own pull.

That distinction matters because learning apps can make the learning challenge feel like a toll booth before the fun begins. A child answers questions, receives coins or animation, then waits for the next reward. The score supplies the reason to continue.

A stronger learning game gives the child a reason to think before the answer arrives. They can see a machine that needs power, a route that leads the train the wrong way, a word that still needs building, or a circuit that has not yet connected. The challenge creates the next reason to return.

For a closer look at how reward loops can take over, read What Happens When the Reward Wheel Becomes the Activity?.

Run the test at an ordinary stopping point

You do not need a special setup. Let your child play for about five minutes, then pause during a normal session. Avoid stopping during a big celebration, because any app can look exciting at its loudest moment.

Ask one simple question: “What were you trying to do?”

Then wait.

A child may answer with a destination: “Build that part of my island.” They may name a problem: “I had to work out which fraction fit.” They may explain a plan: “The train needs to go around the broken track.” Those answers show that the child can connect the activity, their choices, and the result in the world.

If the answer is unclear, ask a second question: “What would you do if you had two more minutes?”

You are looking for a next action that belongs to the child, not a command issued by the app. “I’d try the other path” is useful evidence. “I’d collect the reward” is evidence too. Neither answer makes a child good or bad. The test simply shows what the design is teaching them to value.

Look for learning that changes the world

In Jambolino, a child solves real learning challenges to repair, build, and upgrade places in their own persistent world. Math, reading, logic, science, music, and geography each have playable challenges with a visible purpose. Progress does not disappear when a session ends, and neither does the world they were shaping.

That makes the hand-back question more revealing. A child might say they want to light a structure, complete a route, or return to a problem that felt close to solvable. The learning action and the world action are connected.

The app also avoids ads, in-app purchases, loot boxes, countdown pressure, and streak loss. Those choices leave more room for the child’s own reason to continue. A return moment can welcome them back without warning that they have failed to protect a streak.

Apollo 13’s crew did not keep working because a score rose on a screen. They kept working because the next solution affected the larger situation. A child’s tablet session carries much lower stakes, obviously, but the design lesson holds: give them a real problem inside a world that responds, and the next move can matter on its own.

Use what you hear to choose the next session

Run the test with more than one app, on different days. Write down the child’s exact words. You may notice that one app produces talk about prizes while another produces talk about plans, stories, places, and problems.

Choose more of the experiences that leave your child with a thought worth returning to. When you hand the tablet back, see whether they pick up the same unfinished thread.