From Device Selection to First Validation

Overview

Selecting a cloud device is only one step in the validation flow. The more important question is what happens immediately afterwards.

For Metricon, I wanted this transition to feel continuous and lightweight. Instead of interrupting users with another modal or moving them to a separate Device Details screen, the selected device card changes state and reveals the next action directly within the existing device catalogue.

The result is a contextual transition from device selection to first validation without leaving the current workspace.

Challenge

After choosing a Shared Cloud Device, users need to understand what happens next.

The original interaction relied on a popup presenting applications installed on the selected device. While functional, this introduced another layer into a flow that should be fast and self-explanatory.

For the first Metricon experience, users already have access to a preinstalled demo application. Requiring them to navigate through application management before experiencing the product would create unnecessary friction.

The challenge was therefore to provide a clear next step while preserving context and keeping more advanced device functionality available without forcing users into it.

Design Decision

I explored three possible patterns:

• a modal asking whether to launch the demo application,
• a dedicated Device Details screen,
• a contextual state change within the selected device card.

I chose the third approach.

A modal would interrupt the flow, while a full Device Details view would introduce information that is not yet necessary. The selected-card state applies progressive disclosure: users see only what they need to continue, while detailed device information remains available on demand.

Contextual Device State

After selecting a device, its card changes from a catalogue item into an action state.

Instead of repeating the full hardware presentation, the card confirms the selection and introduces the next step:

Selected Device
Google Pixel 7a
Android 14 · 6.1" · 2340 × 1080

Start with Metricon Demo
Launch the preinstalled demo app and begin validation immediately.

Launch demo app

View device details →

A lightweight secondary action allows users to return and choose another device if needed.

This keeps the hierarchy intentionally simple:

selected device → demo application → validation

Reducing Friction in First-Time Activation

The demo application is already prepared for the user, so launching it also starts recording automatically.

For a guided first validation, there is little value in asking users to separately confirm:

1. the device,
2. the application,
3. the application launch,
4. and then the recording itself.

The interaction therefore removes unnecessary confirmations and moves users more quickly toward the first meaningful product outcome: an interactive validation report.

More advanced use cases can still support choosing exactly when recording begins, but the demo path is intentionally optimized for activation.

Device Details Remain Optional

Selecting a device does not mean users should lose access to its technical information.

The View device details link preserves this capability without making it part of the mandatory first-time flow.

A future Device Details experience can support:

• full hardware specifications,
• custom applications,
• application management,
• validation history,
• device configuration.

This keeps the current interaction focused while leaving room for the product to grow.

Supporting the Commercial Model

The interaction sits inside the same Devices experience that communicates Metricon’s progressive access model.

Free users can immediately select from the Shared Cloud Device pool and launch the demo application, while additional device coverage remains visible through Pro and Enterprise options.

The activation path is therefore never blocked by monetization.

Instead, users first experience the value of remote validation and encounter broader paid coverage in context.

Outcome

The final interaction avoids introducing another screen simply because additional functionality exists.

By transforming the selected device card into the next-step action, Metricon preserves context, reduces interaction cost, and makes the first validation feel like one continuous workflow.

Choose device → Launch demo app → Start validation

The design keeps advanced information accessible, but prioritizes the action that matters most at this stage: helping users experience the product as quickly as possible.

Progressive disclosure made the next step obvious without making the product feel simpler than it really is.

© Zofia Szuca 2024
Brand and product designer

LinkedIn - Dribble - Behance

Privacy Policy | Terms of Service