Testing your app with a small group before launch

Between building and launching there is a short step: a first version tested by a small group of your community. Here is how we look at it. Three markers: who tests, what we observe, what decides the opening.

Aurelio MauriciCo-founder, management, 2 min

Photo: Priscilla Du Preez artographybyp, CC0. Photo credits

Where the test sits

The path has four steps. We talk about your project. We show you your mockup. We build and launch. Your app runs and earns. The test sits in the third.

At that point, payment is connected and the app already installs on the home screen. The group sees what your audience will see.

The site sets neither the size of the group nor the length of the test. I do not invent them here. We set them with you, depending on your niche and your calendar.

Marker 1: who tests

The marker is use. Pick people who already use your content: those who redo your sessions, who ask precise questions, who come back.

Leave out the close friends who will find everything great. A kind opinion teaches you nothing.

Mix the phones if you can. A group entirely on iPhone says nothing about installing on Android.

Marker 2: what we look at

Four moments, in order. Installing on the home screen. The first screen after opening. The payment. The return the next day.

For each, a single question: did the person get there without help? Yes or no. No score out of ten.

A no is worth more than a yes. Ask where it stopped and, if possible, for a screenshot.

Four moments to observe

  1. Installing on the home screen
  2. The first screen after opening
  3. The payment
  4. The return the next day
One question each time: did they get there without help?

What the test does not measure

It does not say how many people will subscribe. A small group you picked is not your whole audience, and nobody knows in advance what the app will earn.

It also does not judge your content on substance. It checks that the app can be understood and that nothing blocks.

Marker 3: what decides the opening

Sort the feedback into two columns. On the left, what blocks: you cannot install, pay or find today’s session. On the right, what annoys: a vague word, a button too low.

What blocks gets fixed before launch. What annoys can wait for an update, since we do those on our side.

When the left column is empty, we open.

Your role during the test

You choose the group and you write to them. A short message is enough: what you ask of them and where to send their remarks. You pass us the list, we fix.

You don’t have to handle technical support. If an installation gets stuck, we take care of it.

Next step

Write down right now five first names from your community to whom you would send the first version. If you cannot find five, that is useful information even before we build.

Keep that list for our first conversation.