Designing a Focused Remote Validation Experience

Overview

Metricon supports both local and remote manual validation.

When users work with a physical device, they interact directly with the application. Remote validation introduces a different interaction model: the application is streamed from a cloud device and controlled through the computer using mouse and keyboard input.

The recording experience therefore needed to support remote interaction without turning the session into a monitoring dashboard.

The final design uses a dedicated Focus Mode that prioritizes the application being tested while Metricon captures evidence, telemetry, logs, and interaction data in the background.

Challenge

The original product combined several responsibilities within the recording screen:

• device and application selection,
• recording controls,
• screenshots,
• telemetry charts,
• annotations,
• logs,
• performance monitoring.

Although this exposed a large amount of information, it also required users to split their attention between performing the validation and analysing the session while it was still happening.

For Metricon, I wanted to separate these activities.

During a manual validation session, the user's primary task is to:

Interact with the application, observe its behaviour, and capture moments that may require further investigation.

Detailed analysis can happen afterwards, when the collected evidence is assembled into the interactive report.

Design Principle

Capture first. Analyse later.

Metricon separates evidence collection from evidence analysis.

During the session, the platform continuously captures the technical context required for later investigation.

This can include:

• screen recording,
• interaction events,
• timestamps,
• telemetry,
• application logs,
• device and application metadata.

These signals remain in the background instead of competing with the test itself.

After the session, they become part of the interactive report where they can be reviewed together with user-generated markers and notes.

A Dedicated Session Mode

Starting a validation session replaces the standard product navigation with a minimal Session Bar.

Instead of:

Dashboard · Devices · Record · Reports

the interface displays only the information required during the active session:

Google Pixel 7a · Metricon Demo

REC · 02:18

End session

Removing the main navigation creates a clear change of mode: the user is no longer browsing Metricon but actively performing a validation.

It also prevents accidental context switching during recording.

Remote Device as the Primary Workspace

The remote device occupies the centre of the interface.

The surrounding UI is intentionally minimal so that the tested application remains the dominant visual element.

The user interacts directly with the streamed application:

• mouse input represents touch interaction,
• keyboard input can be passed into application fields,
• remote controls remain available through contextual help.

The control instructions are not permanently displayed. They are available through the Info action when needed, avoiding persistent instructional clutter once users understand the interaction model.

Automatic Recording for the Demo Experience

The first Metricon validation uses a preinstalled demo application.

In this guided flow, launching the demo application also begins recording automatically.

Adding another explicit Start recording step would create an unnecessary confirmation between:

Launch demo → Start recording → Validate

Instead, the first-time flow becomes:

Launch demo → Validate

The active recording state remains clearly visible through a dedicated recording capsule:

● REC | 02:18

The red recording indicator communicates an important system state without dominating the interface.

For future professional workflows, application launch and recording can remain separate when users need to navigate to a specific point before evidence capture begins.

Marking Important Moments Without Breaking Focus

Manual testing frequently produces moments where something looks unusual but stopping immediately to describe it would interrupt the task.

Metricon therefore introduces Mark moment.

A single action creates a timestamped marker in the session.

The marker can later be connected with the technical evidence captured around that point, including the recording, telemetry, and logs.

The interaction is intentionally lightweight:

Mark moment
Save this point on the timeline for later review.

Instead of forcing users to explain the issue immediately, Metricon preserves the moment so it can be investigated during report review.

Notes When Context Matters

Sometimes a timestamp alone is not enough.

The secondary Add note action allows the user to attach context to the current point in the session.

Add note
Add a note to this point in the session for later review.

Both actions support the same underlying idea:

Mark moment
Capture the point quickly.

Add note
Capture the point together with immediate context.

This allows users to choose the level of interruption appropriate to the situation.

Session Tools

Only three contextual actions remain next to the remote device:

Mark moment
Create a timestamped marker for later investigation.

Add note
Attach written context to the current session point.

Remote controls
View mouse, keyboard, and session shortcut controls.

The toolbar remains visually secondary to the application stream while keeping the most useful testing actions within immediate reach.

Ending the Session

End session is separated from the recording indicator.

Recording status communicates what the system is currently doing.

Ending the session is an explicit user action.

Once the validation ends, Metricon can process the captured evidence into the next stage of the workflow:

Session → Evidence → Finding → Report

The user can then analyse the material with significantly more context than was available during the live session.

Key Design Decisions

Remove telemetry from the active workspace
Performance data and logs are captured continuously but analysed after the session.

Replace product navigation with a Session Bar
The interface communicates a dedicated work mode and removes unnecessary navigation choices.

Make the remote application the visual priority
The tested product—not Metricon's own interface—receives most of the available screen space.

Automatically record the guided demo
The first validation removes unnecessary setup steps and gets users to product value faster.

Separate marking from describing
Users can capture an important moment instantly and add detailed interpretation later.

Keep advanced controls contextual
Remote interaction instructions remain available without permanently occupying screen space.

Outcome

The redesigned recording experience changes Metricon from a monitoring-heavy interface into a focused manual validation environment.

Instead of asking users to simultaneously test, monitor, interpret, and document the application, Metricon supports a clearer division of work:

During validation

Interact
Observe
Mark important moments

After validation

Review evidence
Investigate telemetry and logs
Create findings
Build understanding

This creates a cleaner relationship between the active session and the evidence-based decision workflow that follows.

Metricon captures complexity in the background so the user can stay focused on the application in front of them.

© Zofia Szuca 2024
Brand and product designer

LinkedIn - Dribble - Behance

Privacy Policy | Terms of Service