For iPhone and Android apps

Real phones. Real thumbs. Real confusion.

Ten people install your app on their own phones and talk through it. You see every tap and hear every "wait, how do I go back?"

iPhone, Android, or bothTestFlight or Play test tracksTheir own phones, not emulators
Oil painting: a young man in a white shirt reading something on his phone by a window.

Why phones are harder

Small screens hide big problems.

Gestures

Swipes nobody discovers

If an action only lives behind a swipe or a long press, most people never find it.

Permissions

Asked before trust

Notifications, location and contacts requested on the first screen. Testers say no, then the app doesn't work.

Size

Fine on your phone, not theirs

A smaller screen, larger text, an older device. Testers use what they really own.

Oil painting: a young woman in a blue veil tapping through an app on her phone, hills behind her.

What you send us

A test build and three tasks.

Send a TestFlight invite, a Google Play test track, or a store link. Say which phones matter and we'll match testers who own them.

Example brief

The product

A meal planning app that builds a weekly shopping list.

The testers

Parents who cook at home at least four times a week. Half on iPhone, half on Android.

Tasks

  1. Install the app and plan three dinners for this week.
  2. Turn your plan into a shopping list and tick off two items.
  3. Find where you would tell the app you don't eat meat.

Questions to answer out loud

  1. Which screen confused you the most?
  2. Would you allow notifications from this app? Why?
  3. What would make you open this again next week?

What testers usually find

Four things phones always expose.

Common find

Permission asked too early

Ask after people see why it helps, and far more of them say yes.

Common find

Icons without words

A row of icons you know by heart. Testers guess, and guess wrong.

Common find

The keyboard covers the button

Testers type, then can't find how to continue. It happens on smaller phones most.

Common find

The intro slides get skipped

Nobody reads the carousel, so the tips in it never land.

New Google Play account?

Two things, both covered.

Publishing on Play

The 12 testers rule

New personal Google Play accounts need 12 testers opted in for 14 days before they can publish. Our pack gives you 16 real Android testers for $39.99.

How the 14 days work

Free tool

The 14-day tracker

Enter the day your testers opted in and see which day you're on, when you can apply, and whether your margin is safe.

Open the tracker

Which test fits

Usability, closed testing, or both.

Most apps

Standard test

$79

Ten matched testers on their own phones, up to ten minutes each, with a designer's fix list. iPhone, Android or a mix.

Book a test

New personal Play accounts

Google Play pack

$39.99

Sixteen real Android testers opted in to your closed test for the full 14 days, with replacements if anyone drops out.

Get 16 testers

Mobile app questions

Before you start.

No. TestFlight for iPhone, and internal or closed testing tracks for Android, both work. A live store link works too.

Yes. Tell us the split you want, like five and five, and we match testers who own those phones.

Yes. Testers record their screen and voice, so you see every tap and hear what they expected to happen.

Yes. A clickable prototype link works if the app isn't built yet. Testers use it on their phones.

Read next

For app makers.

Get started

See your app through a stranger's eyes.

Your first test is free: three matched testers and a short fix list. No card.

Rather be on the other side? Become a tester