Product storytelling / Usage guideSEPTEMBER 2026

How to use Nexus /

A practical path through Nexus, from the first input to a saved, reviewable result.

Terracotta product photography, expansive typography and a warm editorial rhythm introduce Nexus. A separate interactive studio collection lets visitors inspect the original interface geometry.

Before you begin

Begin with the brand experience, then follow its primary action into the interactive studio or private workspace.

Create an account in Nexus and work in its own private workspace. Accounts and records from another Lumia product are separate. Product teams presenting a technical device family and prospective buyers who need to understand configurations before requesting a walkthrough.

Follow the workflow below to understand the application. Contact Lumia for a guided walkthrough; account access is private. An exported file reflects the record at the time of export.

01

Inspect the device as an object

Open a product and rotate its actual model to understand the enclosure and connections. Use wireframe or exploded inspection when the parts matter to the discussion. Read the specifications alongside the model. The original One and Pro collection gives the demonstration a coherent family instead of unrelated decorative objects.

02

Choose a compatible setup

Select accessories for the intended setup. An incompatible accessory choice replaces the conflicting option in the tested interface, while the server validates the submitted selection. Check the resulting labels before proceeding. A rack installation and an angled desktop arrangement should remain distinct configurations rather than an impossible combined list.

03

Save the comparison you actually reviewed

Choose up to three distinct products and save the comparison after making the accessory choices. Reopen it to recover those selections alongside the saved specifications. If you change an accessory, save again before using the updated comparison. Download its PDF when you need a readable selection summary for another conversation.

04

Carry the configuration into a request

Use the saved comparison to request a walkthrough and supply the required contact details. The stored request retains the chosen products, accessories and specification context. It gives an operator something concrete to review. It records a request; an appointment, sales commitment or external email delivery requires a separately confirmed action.

Operating the product

Save the comparison again after changing an accessory so the exported and requested configuration matches the latest choice.

Resolve invalid or incompatible accessory errors against the current product catalogue before retrying.

Keep source models and their rights records when importing a new product.

Review the request’s retained specification and selection before confirming a walkthrough with the visitor.

Verify any external scheduling or notification integration independently before claiming that a request reached a recipient.

APPLY THE THINKING

A similar problem in your business?

Bring a real workflow, representative inputs and the result that needs to be reliable.

Shape a project brief