Web and mobile apps

The same method, behind the login and on the phone.

Onboarding, settings, the checkout inside your app: the places public tests cannot reach are often where people give up. Test a web app behind a login, or upload your mobile app (Android or iPhone).

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.

Example session

Office manager, new to the tool · desktop Task: Invite a colleague to the workspace

  1. DoesLogs in with the test account. The model only sees “login: ok”.
  2. Expects“There will be a Team page in the sidebar.”
  3. DoesOpens Settings → Workspace → Members.
  4. Says“Inviting people is under Settings? I nearly gave up.”

Example cost: 3 profiles × 2 tasks × 2 formats = 12 sessions × 2 credits = 24 credits

Before your first web app test

  1. Verify the domain

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

    ExampleTXT uxsurgery-verify=7f3c… (illustrative)

  2. Add test accounts

    Stored encrypted and used only to log in.

    Exampletester1@staging.yourapp.example

  3. Write two or three tasks

    Short, realistic goals in your users’ words.

    Example“Export last month’s invoices as PDF”

  4. Run and review

    Videos, every problem ranked (the 3 worst first) and a fix prompt, as with any study.

    Example#1 High · Invite link hidden in Settings · 3 of 6

How we handle credentials

Mobile apps (Android and iPhone)

Android: Pro plan and above, 2 credits per session · iPhone (beta): Agency plan, 10 credits per session

  • Create a mobile app project and upload your app: the APK for Android, the .ipa for iPhone. It does not need to be in a store.
  • Add test accounts if the app needs a login. Skip them if people can use it without signing in.
  • Pick tasks: “book a table for tonight”, “change the delivery address”, “turn off notifications”.
  • AI agents install your app on a phone and use it like your customers: they tap, type, scroll and go back. Every session is recorded.

Android apps (you upload the APK); the free first UX test works with an APK too. iPhone apps on real devices (beta): you upload the .ipa, on the Agency plan.

Example session

Commuter booking on the way home · phone Task: Book a table for two tonight

  1. DoesOpens the app and skips the three welcome screens.
  2. Expects“There will be a Book button on the restaurant page.”
  3. DoesTaps a restaurant, scrolls past the photos and the menu.
  4. Says“Where do I book? I had to scroll to the very bottom.”

Example cost: 3 profiles × 2 tasks = 6 sessions × 2 credits = 12 credits

Current limits

No payments
Agents stop before paying, inside web and mobile 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.
Mobile app reports may have no mockups
They always include the videos, every problem ranked and the fix prompt. Before/after mockups may not be included.

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.

3 AI agent sessions on your site, the 3 worst problems and a video.