DEV Community

Sam Ellis
Sam Ellis

Posted on

Designing a city game for people who will only give it three minutes

A lot of people will try a city scavenger hunt for about three minutes. Not because they hate it - because they are standing in a street with a coffee in one hand, a phone in the other, and somewhere else to be.

Design for those three minutes and the rest follows. Here is what we have learned about them.

The first glance is doing most of the work

When somebody opens the app, they are not reading. They are glancing at a phone screen while walking, in poor light, possibly with a backpack in the way.

That means the very first thing on the screen has to say what is happening. Not a slogan, not a logo animation - the actual instruction for the first stop. If the first thing they see is an explanation, they will read it later, and later never comes.

The same reasoning applies to the first photograph. It has to look like something they might find, because the first stop sets the expectation for every stop after it. Give somebody an opening shot that is unusual, and they will spend the rest of the hunt looking for unusual things that are not there.

The first "not quite" is the tone

The moment that matters most is the first time the app says the photograph is not right. It is going to happen, and it will happen within the first two minutes for most people.

If that message feels like a failure, the hunt is over. If it feels like a nudge - look again, you are close - then it becomes the normal texture of playing. The person is not failing a test, they are looking at a street and being asked to look slightly harder, and the wording has to say that.

This is the same reason the stops are written the way they are. "The blue door with the number on it" gives you something to look for. "The building" does not.

One stop at a time

It is tempting to show the whole route on a map, every stop at once, so the player can see the shape of the thing.

Resist it. A list of eight pins on a map tells somebody they have eight errands. What we want is a person walking and looking, which is a completely different posture, and the moment you show the whole route you have turned a walk into a checklist. Keep the route present but keep the next stop the loudest thing on the screen.

Three minutes in, they should be walking

Here is the test we apply: three minutes after opening the app, is somebody actually moving through a street, and are they looking at things rather than at the phone?

If the answer is no, the problem is almost always that the first stop is too far away, or too ambiguous to attempt, or too easy to pass by. Fix the first stop and the first three minutes take care of themselves.

We wrote up the flow in more detail, with screenshots, on our docs page: pinghunt.com/docs. And the short version of how it works is here: pinghunt.com/how-it-works.

The general rule, if you are building something like this: the first thirty seconds decide whether the next thirty minutes exist. Spend them accordingly.

Top comments (0)