ENDE
Start creating

Learning path

Pocket Code intro

A first session with Pocket Code, the free app behind this project's original trials. By the end of one sitting, your child has a small game running on their own phone.

Age
8 and up
Time needed
One sitting, 45–60 minutes
You need
A smartphone, no prior experience
A single chunky brick hovering just above a small stack of two identical bricks, about to be set down.

What happens in the session

  1. 01

    Set up your first project

    Open Pocket Code on the phone you'll be using and start a new, empty project. Choose one simple object to begin with. Exactly which menu you use to do this is not fixed, only that you end up with a project open and a single object sitting on an otherwise empty stage. If you're helping a child through this, let them do the tapping.

  2. 02

    Get one thing moving

    Add an instruction that makes your object move or respond, for instance moving a short distance, or reacting when it's tapped, then run the project to see it happen. The exact block or menu path depends on the version in front of you, so treat this as an experiment rather than a set of fixed clicks. Run it, watch what happens, change one thing, and run it again. That loop is the actual skill being learned.

  3. 03

    Give it a goal

    Turn the moving object into something with a point: a target to reach, an obstacle to avoid, or something to collect, plus a simple way to tell whether that has happened. Keep it to one screen and one action rather than reaching for levels or a score. By the end of the session, there should be one small thing your child can hand you and ask you to play.

What you need

This path assumes nothing beyond a phone. Pocket Code, the free programming app behind this project, runs entirely on the device itself, so there is no separate computer to set up and nothing to install first except the app. If a parent or teacher is nearby to help for the first few minutes, that is enough; nobody helping needs to already know how to code.

Set aside one session and treat it as a single sitting rather than a lesson plan spread across a week. The point of this path is to prove, in about an hour, that the thing behind a game is something a child can direct rather than only receive. A quiet, unhurried hour works far better than the last twenty minutes before dinner.

Why the first result should stay small

The instinct, especially for an adult helping, is to aim for something that already looks like a real game: several levels, a score, sound effects. Resist that instinct for this first session. What matters is the loop underneath any of it, changing something, running the project, seeing what happened, and changing it again, not how finished the result looks.

A single object that moves when tapped is already a win. A shape that bounces off the edges of the screen is a win. Success here is not measured by how impressive the result looks to an outsider, it is measured by whether your child made a choice, watched it take effect on the phone, and wanted to try one more thing.

Typical stumbling blocks

A handful of things derail a first session more often than the programming itself does:

  • Aiming too big from the start. A full game with rules and scoring belongs to a second or third session, not the first.
  • Reading every menu before touching anything. It is faster, and closer to how programming actually works, to try something first and see what happens.
  • Treating an unexpected result as a mistake to hide. An object moving the wrong way is information, and often the most interesting moment of the session.
  • Taking the phone to fix things quickly. The value sits in your child's own hand on the screen; talking through the next thing to try is more useful than doing it for them.
  • Expecting the interface to match a screenshot somewhere. Pocket Code changes between versions, so exact labels and menu names may differ from what is described here; this path describes what you do, not what to tap.

Where it goes next

One playable thing is the finish line for this path, not for coding as a whole. The next step on this site is Game logic in class, which takes the same raw material, objects that move and react, and turns it into an actual game with rules, built around real lesson slots for a classroom, though a motivated family can work through it just as well at home.

If you want to know more about the app itself, including where it came from and why this project is able to offer it for free, the Pocket Code page on this site covers that history. None of it needs to be understood before you start; it is background for afterwards, not a prerequisite.