Remote playtesting means players take part from home, on their own devices, while the session is recorded and studied from somewhere else. It suits mobile games well. Players hold the phone they always hold, in the room they usually play in, and the team can recruit from any country the game launches in.

Much of the remote user testing advice online is written for websites and apps. The workflow is similar for games, and it changes in two places: capturing gameplay, and getting consent to record it. Below is the full workflow in order, with the most space given to those two.

1. The question

Write down the decision the study is meant to inform, in one sentence, before you do anything else. "Find out why players who finish the tutorial don't start level 2" is a question a remote study can answer. "See what players think of the game" is too open to point to any decision.

The question decides everything after it: which build to send, who to recruit, how long the session runs, and whether a researcher needs to be present. If you cannot fit it in one sentence, it is probably two studies. Playtesting methods: which one answers which question can help you match the question to a method.

2. The build

A remote build has to work without anyone from the team there to fix it.

• Distribution. iOS builds usually go out through TestFlight. Android builds go out through a closed testing track on Google Play or a direct APK. Check the install steps yourself on a clean device before sending them to participants.

• Starting state. Decide where the session begins. A first-time user experience (FTUE) study needs a fresh install with no saved progress. A study of level 20 needs a save file or a debug skip that drops the participant there.

• Stability. A crash that a researcher in the room could sort out in a few minutes will often end a remote session. Test the build on the low-end devices your audience uses.

• Debug elements. Remove developer overlays, frame counters, and cheat menus, or participants will find them.

• Telemetry. If the build logs events, make sure they can be matched to each participant's session, so you can check what the event log recorded against what you see in the video.

3. Recruitment

Recruit against the same criteria you would use for a paid UA campaign: genre, platform, device tier, region, and spending habits if they matter to the question.

Screen out people who have played the game before, and anyone who works in games, unless the study is specifically about them. A screener of five to eight questions is usually enough. Include at least one question that catches people who answer screeners carelessly, such as asking which of a list of games they have played and including one that does not exist.

Remote studies tend to lose more participants than lab studies. Some never install the build, some have camera problems, and some do not show up. Recruit one or two more people than you need for each segment. Emhance studies can recruit from our own gamer panels or use your players.

For how many to recruit in the first place, see how many playtesters do you need?

4. Setup: capture and consent

Capture and consent take more planning in a game study than in a website study.

Gameplay capture

Recording gameplay is harder than recording a browser tab. The study needs a moving game screen at a usable frame rate, captured without slowing the game down, on a device the team has never seen.

You usually need three streams:

• The screen. iOS and Android both have built-in screen recording, and many remote usability testing platforms provide an SDK or companion app that captures the screen alongside other data. For fast games, check that the recording keeps up with the action. A choppy recording of a rhythm game is very hard to analyze.

• The player. A front-facing camera recording shows where the participant hesitated, smiled, frowned, or looked away. On a phone, the front camera does this without extra hardware.

• Audio. If participants think aloud, or if a moderator is present, you need clear audio. Game sound can drown out speech, so decide in advance whether participants play with sound on.

All three streams need to line up in time. A moment of frustration on the participant's face means little if you cannot see what was on screen at that second.

At Emhance, participants play on their own device in their own home, with a camera recording their face. We analyze facial expressions and eye movement second by second and match them to the screen recording. We count a moment as engaged when emotional intensity and concentration are both high, and each moment is tied to what the player was doing at the time. No special hardware is needed. You can try the blink signal behind concentration in our 30-second demo game, and see how Emhance playtesting works.

Consent

Recording a participant's face, voice, and screen at home involves more personal data than a website click-through, so consent needs to be explicit and specific.

A consent form for a remote playtest should state:

• What is recorded. Screen, face, voice, and any telemetry, each named separately.

• Who sees it. The research team, the wider studio, or any third party analyzing the data.

• How it is used. For research only, or also for internal presentations, highlight reels, or marketing.

• How long it is kept, and how participants can ask for it to be deleted.

• Confidentiality. An unreleased build usually needs a non-disclosure agreement. Keep it short and readable.

• Payment. How much, when, and whether it depends on finishing the session.

Participants playing at home can also capture things you did not intend to record: notifications, other people in the room, messages that appear on screen. Ask participants to turn on Do Not Disturb before they start, and tell them they can pause or stop at any time.

Where a study recruits participants in more than one region, check whether local data protection rules, such as GDPR in Europe, set extra requirements for recording faces.

5. The session

Send instructions that a participant can follow without help. Include install steps, a short check that the camera and screen recording work, and the length of the session.

For a moderated remote session, a researcher joins by video and can ask questions as the participant plays. For an unmoderated session, the participant plays alone and answers questions afterward. Moderated or unmoderated: choosing for games covers which suits which question.

Keep the session focused on the question. An FTUE study usually covers the first 10 to 15 minutes of play, with a short interview before and a debrief after. Ask participants to play the way they normally would. "Play until you'd normally put it down" shows you where they would actually stop, which "complete the tutorial" cannot. Our Beginner's Guide to FTUE Playtesting covers session design in more detail.

6. Analysis

Start by watching every session in full, once, before drawing conclusions. Note each moment where something happened: a hesitation, a failure, a moment of delight, a comment.

Then look for repetition. A friction point that shows up in four of six sessions is worth acting on, while one that shows up once may come down to that one participant. Group the moments by where they happened in the game, and check them against telemetry where you have it.

Keep each finding tied to a timestamp and a clip, and write it in enough detail for a designer to act on, for example: "Four of six participants stopped at the crafting screen for over 20 seconds, and three asked where the materials came from."

7. The decision

Go back to the one-sentence question from step 1 and answer it. Then list what should change, in order of how much each change matters to that question.

Good outputs from a remote playtest are specific: move this prompt, cut this screen, explain this currency earlier, leave this hard level alone because players were engaged in it. Each recommendation should link back to the sessions and moments that support it.

Peaksel's study of The Vault followed this path. Analytics showed players dropping off before level 3. In a study with six participants, engagement dropped consistently within the first 45 seconds of live gameplay. The tutorial had taught players to work on a single vault face, and the live game asked them to explore several. Peaksel redesigned levels 1 to 3, and reported 9.6% more users completing level 3, 7.3% more reaching level 10, and a 14.5% total LTV uplift. The Peaksel case study covers the full study.

What to look for in a remote usability testing platform

If you are choosing a remote usability testing platform for games, check these points against your own build:

• Can it record the game screen smoothly at the frame rate your game needs?

• Does it record the participant's face and voice, and keep all streams in sync?

• Can it recruit players who match your audience, by genre and device, in the regions you need?

• Does it handle TestFlight and Android test builds, or only web links?

• How does it handle consent and data retention, and where is data stored?

• What does it deliver at the end: raw recordings, tagged clips, or analysis tied to specific moments?

For the bigger picture, see game user research: what it is and what teams use it for.

Book a demo to see a remote Emhance study run on your own build.