Apps & Android

The same method, behind the login.

Onboarding, settings, the checkout inside your app: the places public tests cannot reach are often where people give up.

Web apps with login

Pro plan and above · 2 credits per session

  • Verify your domain once with a DNS record or a file on your server.
  • Create test accounts for us. Use staging if you have it, never real customer accounts.
  • Pick tasks: “invite a colleague”, “export last month’s invoices”, “change the plan”.
  • Agents log in through a separate step. The model never sees the password, only that the login succeeded.

Android apps

Agency plan and above · 3 credits per session

  • Each study runs on a dedicated, clean Android emulator that is deleted afterwards.
  • Provide an APK or a build from your internal test track.
  • Taps, swipes and typing are recorded as video, like in web sessions.
  • The same profiles apply: reduced vision, imprecise taps, hurry, low digital skill, no context.

Before your first app test

  1. Verify the domain

    Add the DNS TXT record or upload the file we give you.

  2. Add test accounts

    Stored encrypted and used only to log in.

  3. Write two or three tasks

    Short, realistic goals in your users’ words.

  4. Run and review

    Videos, the 3 worst problems and a fix prompt, as with any study.

How we handle credentials

Current limits

No iOS yet
We only test Android apps for now.
No payments
Agents stop before paying, in apps too. Use a test mode or skip that step in your tasks.
No two-factor codes
Test accounts need a login that works without a code sent to a phone.

See where people get lost on your site.

Paste your URL. In a few minutes you get the 3 worst problems and one session video.

Free. No card. 3 sessions, the 3 worst problems and a video.