Designing Device Access for Progressive Coverage

Overview

Metricon supports two complementary validation models: users can work on their own local hardware or access shared cloud devices provided by the platform.

The challenge was to design a single Devices experience that makes both options immediately understandable while supporting a scalable commercial model.

Instead of restricting the core validation workflow, Metricon keeps local validation unlimited and monetizes the infrastructure required to expand device coverage.

The resulting experience combines device discovery, local hardware access, progressive plan limits, and upgrade opportunities within one coherent workspace.

Challenge

Device access is one of the most important parts of Metricon because validation quality depends on testing across different hardware, operating systems, screen sizes, and form factors.

At the same time, cloud devices generate real infrastructure costs.

The product therefore needed to balance three goals:

• provide enough value in the Free plan to demonstrate the complete workflow,
• allow users to work without artificial restrictions on their own hardware,
• create a natural reason to upgrade when broader device coverage becomes necessary.

The key question became:

How can device access scale from individual validation to enterprise infrastructure without making the Free experience feel intentionally crippled?

Product Model

Metricon separates ownership from coverage.

Local Devices
Users can connect and validate on their own hardware without usage limits.

Shared Cloud Devices
The Free plan includes a selected pool of cloud devices that allows users to experience remote validation immediately.

Expanded Cloud Coverage
Paid plans unlock additional models, form factors, and device configurations.

Dedicated Device Pools
Enterprise customers can access infrastructure reserved specifically for their organization.

This creates a progressive infrastructure model:

Own hardware → Shared cloud coverage → Expanded coverage → Dedicated infrastructure

One Devices Workspace

Rather than creating separate areas in the main navigation, both infrastructure models live inside a single Devices module.

The interface provides two clearly visible entry points:

Shared cloud devices
Local device

The Shared Cloud view is selected by default during first-time onboarding because it provides a predictable environment for the guided demo flow.

Local validation remains visible at all times, allowing users to switch to their own hardware without leaving the screen.

This keeps the information architecture simple:

Dashboard → Devices → Record → Reports

while treating Local, Shared Cloud, and Dedicated Pools as different infrastructure models rather than separate products.

Free Plan as a Complete Starting Point

The Free plan includes nine Shared Cloud Devices.

The device carousel is intentionally prominent because first-time users should be able to browse available environments visually and start validation with minimal setup.

Each device card communicates only the information required for selection:

• device model,
• operating system,
• display size,
• resolution,
• storage,
• current availability.

The current state is communicated explicitly through Available now, while a single Choose device action continues the workflow.

The carousel makes the first experience visual and approachable without turning the screen into a technical inventory table.

Monetizing Coverage, Not the Core Workflow

The paid-device catalogue appears directly below the Free selection.

This was an intentional product decision.

Instead of hiding unavailable capabilities until users encounter a paywall, Metricon makes the broader device ecosystem visible from the beginning.

Users can immediately understand:

The product already supports more environments than my current plan gives me access to.

Paid models are shown with clear access labels:

PRO

or

ENTERPRISE

and a locked state with:

Upgrade to access

This allows monetization to become part of product discovery rather than an interruption later in the workflow.

Why the Paid Catalogue Expands Coverage

The paid catalogue is not designed as a collection of arbitrarily newer phones.

It introduces environments that materially broaden validation coverage.

For example:

• premium flagship phones,
• larger displays,
• foldable devices,
• tablets,
• newer platform generations,
• specialized enterprise infrastructure.

This makes the upgrade rationale more credible.

The user is not paying simply because Metricon has placed a lock on another phone.

They are paying because their validation requirements have become more complex.

Search and Filtering

The Free carousel is optimized for exploration.

The paid catalogue is optimized for discovery at scale.

Users can search by:

• device model,
• operating system,
• manufacturer,

and refine results through lightweight filters such as:

• Android,
• iOS,
• availability,
• plan,
• recency.

This creates two complementary interaction models within the same screen:

Browse when you are exploring.
Search when you know what you need.

As the catalogue grows, the experience can scale without changing the underlying information architecture.

Local Validation as a First-Class Option

The local-device panel remains visible next to the cloud catalogue.

This is important because cloud infrastructure is not positioned as a replacement for hardware the user already owns.

The panel communicates three core benefits.

Unlimited
Local validation has no platform usage limit.

Private
Validation data can remain on the user's own machine.

Reusable
Connected hardware can be reused in future sessions.

The primary action is deliberately simple:

Connect local device

This provides an immediate alternative to the cloud path without competing visually with the main device catalogue.

A Scalable Local Device Pattern

The local-device panel is also designed as a contextual area rather than a static promotional card.

For a new user, it introduces local connectivity.

Once devices have been used, the same area can evolve to surface the most relevant local context—for example a recently used device, connection status, or quick access back to a known configuration.

This allows local hardware to become part of an ongoing validation environment rather than a one-time connection step.

Contextual Upgrade

The paid catalogue ends with a simple question:

Need broader device coverage?
Upgrade your plan to access more device types, newer models, and advanced validation environments.

The interface provides two different commercial paths:

Compare plans

for users evaluating standard paid access,

and

Request enterprise access

for organizations that require dedicated infrastructure.

This separates self-service growth from enterprise procurement without introducing either path too early.

Key Design Decisions

Unlimited local validation
The core workflow remains usable without forcing users into paid infrastructure.

Nine cloud devices in Free
The Free plan provides enough variety to demonstrate the value of remote validation rather than functioning as a superficial trial.

Visible paid catalogue
Users can discover what additional coverage exists before they encounter a limitation.

Coverage-based monetization
Paid plans expand the range and type of environments available rather than arbitrarily restricting basic actions.

Local and cloud in one module
Different infrastructure models remain part of the same mental model: Devices.

Browse first, search when needed
The interface changes from visual exploration to structured discovery as the user's intent becomes more specific.

Business Strategy

The Devices experience translates Metricon's commercial model directly into product architecture.

The progression is not:

Free features → blocked features → upgrade

but:

Current coverage → broader coverage → organizational infrastructure

That creates a much more natural growth path:

Individual user
Local devices + selected shared cloud access

↓

Professional user or team
Expanded cloud catalogue

↓

Organization
Greater coverage and collaboration

↓

Enterprise
Dedicated Device Pools and organization-specific infrastructure

The commercial model therefore scales with operational complexity rather than relying on arbitrary feature restrictions.

Outcome

The final Devices experience brings together two very different infrastructure models without making the product feel fragmented.

Users can:

• start immediately with a Shared Cloud Device,
• connect their own hardware at any time,
• understand what their current plan includes,
• discover additional device coverage,
• search a growing catalogue,
• and upgrade only when their validation requirements justify it.

The result is a device-selection experience that supports both user activation and product monetization, while keeping the core validation workflow accessible from the Free plan.

© Zofia Szuca 2024
Brand and product designer

LinkedIn - Dribble - Behance

Privacy Policy | Terms of Service