At the third visit, your clients use a real, running version of your app for the first time. As at the second visit, your job is to watch and listen. See Preparing to Share Your Ideas: the missions, taking turns, and “don’t rescue” all still apply.

What “working” means this time

You have had several classes to build, and you chose what to build. Your app will not be finished, and it does not need to be. Whatever runs, your clients try; whatever does not, they try on paper. The visit is most useful when:

  • Some path through the app runs from start to finish, so each child can choose, tap, answer, and see what happens.
  • Your procedure runs on your list somewhere a child reaches, so you can watch what they make of its output.
  • Everything else can still be paper. Screens you have not built yet can be frames on your storyboard from the last visit. A child taps the real app, then you point to the next frame. That is normal.
  • Looks can wait. Plain buttons and default fonts are fine. Big enough to tap is not optional: see Designing for Young Users.

If part of your app is not running yet, test that part on paper. Tell me before we leave.

Before we leave

What is different about a real app

A real app shows things paper cannot. Watch for:

  • Waiting. Does the child know something is happening? Do they tap again, and again?
  • Taps that do nothing. Where do they tap that is not a button?
  • Wrong answers and mistakes. What does your app do when a child does something unexpected? Is it forgiving?
  • Reading. Do they read the words on the screen, or guess? Do they ask you to read them?
  • Your procedure’s output. Is what appears after they choose what they expected? Does it ever show nothing at all?

Taking turns

One child uses the device at a time while the others watch. You sit beside them, hold nothing, and say as little as possible; jot notes between turns. Nobody touches the device while a child is using it, unless the app has frozen. Between turns, go back to the start screen so every child starts from the same place.

Don’t rescue

When a child gets stuck, wait. Count to ten in your head. Then ask “What do you think you should do?” Only if they are really unhappy, help, and write down exactly where it happened. That spot is the most useful note on your page.

Your feedback sheet

Use the sheet I provide:

Who (first name)MissionWhat they didWhat the app didWhat they saidWhere they got stuckTheir ideas

First names only, never a last name. No photos, and no screen recordings, of the children or of the app while a child is using it.

At the end, ask the closing questions from How to close. Do not promise a feature or a date.

Before we leave LDPS, take five minutes to fill in anything you remember that is not on the sheet yet.