UX and digital experience research
Remote UX research watches people use a website, app or prototype and hears why. On Qualzy, they use it on their own device, in their own time, and think aloud as they go. You see where they hesitate and give up, with their reasons transcribed and summarised as each recording arrives.
Pick the stage your product's at, or run something that's not here at all. Plenty of teams come back for the next stage.
People use your product on the phone or laptop they'd normally use, and narrate what they expect and what happens instead. Run it before a redesign to find the friction, or after launch to see how the product is really used compared with how it was designed to be used.
Share a link to a clickable prototype and watch people find their way through it. It's the walkthrough you'd run in a UX lab, on the device people actually use. Put screens or wireframes into a Pin Task to see what people notice first and what confuses them.
Follow people from first search to checkout, with commentary at every step, or have them talk through a competitor's site or the app they use today. You hear what works for them before you design the alternative. For the whole path to purchase, add customer journeys.
Ask someone about a site afterwards and you get a tidy summary. The recording keeps everything the summary leaves out. Three illustrative examples:
"Checkout was fine."
Forty seconds looking for the promo code box, then a sigh and carrying on without it.
"I'd use the filters."
Scrolled past the filters twice, then typed the product name into search instead.
"Signing up was quick."
Three goes at a password the rules kept rejecting, narrated with growing irritation.
People record their screen while they work through your task and think aloud as they go, so every hesitation and wrong turn comes with an explanation. On a computer, recording starts in the browser with one permission click. On a phone, they use the phone's own screen recorder and add the recording to their response. The narration arrives transcribed, so you can read a session as well as watch it.
Upload a screenshot, a webpage or a wireframe. People drop pins on what draws them in, worries them or confuses them, tag each one and say why. The pins build into a heat map, with the reasoning attached.
Give people your features, content or menu items as cards and let them group them. An open sort shows the categories people would create and name themselves. A closed sort tests the structure you already have.
A first session shows you first impressions. A diary over the following days or weeks shows you what happens next: whether people come back, which features stick and where they drift away. Repeated entries, with screenshots and photos, track how use changes over time.
People take part from an invitation link in their browser, with nothing to install, and do the task alone, in their own setting, the way they normally would.
Within one project you can split participants into groups and give each group a different version, prototype or task, then compare what happened across them.
Most UX studies run as a Qualzy Discussion of a few days. If you test with the same users release after release, run it in a Qualzy Community and go back to them whenever you have something new.
For a walkthrough you want to steer as it happens, run it as an interview in Qualzy Live, in the same project, and analyse it alongside the recordings.
No. They open the activity from their invitation link in a browser. On a computer, screen recording starts with one browser permission click. On a phone, they use the phone's built-in screen recorder and add the recording to their response.
Yes. Share a link to a clickable prototype in the task prompts and people narrate their way through it, the same way they would with a live site or app.
As long as your task needs. In the University of Bristol study, recordings averaged 11.4 minutes. Every recording is transcribed and summarised as it arrives, so long sessions don't mean long hours of watching.
Yes. Put participants into groups within one project and give each group its own version, prototype or task, then compare the results side by side.
You can pay per project or subscribe, whichever suits how often you research, and AI features are included on every plan. Find out more about pricing.
The site, the app or the prototype, who uses it and what you need to find out. We'll suggest the tasks, and how many people you'll need to see a pattern.
