How do I identify a real product's demo screen without implying it is the default interface?

Identify the screen’s operating state

Ask the merchant whether the screen is factory default, a store demo mode, a configured user view, or a connected-app state. Record the actual device model and software version where available. A single display photograph does not establish how a new customer reaches that view.

Confirm whether the demonstration uses sample data or real user content. Avoid exposing private account information in the reference. The point is to explain the display’s role, not reproduce another person’s records. Keep a separate note for the default delivered state so the two cannot be accidentally merged in copy.

Link every attractive feature to a confirmed condition

If the screen requires setup, an account, a subscription, a network, or an additional device, obtain those conditions from the merchant’s actual documentation. Do not infer them from icons. A chart on a demo screen can illustrate a view without proving live measurement or an included service.

Use factual language such as demonstration view when that is what the source supports. Do not fabricate a startup interface or replace a real screen with a polished generic dashboard. Review visual content and explanatory text together; a tiny disclaimer cannot cure an entirely invented product function.

1. Confirm device model and source ownership.
2. Identify default, demo, configured, or connected state.
3. Record documented setup and service conditions.
4. Compare the actual screen with the proposed visual and wording.
5. Hold any feature or access claim without evidence.

A fictional countertop display

Fictional exercise: a rechargeable countertop product shows an animated showroom dashboard, while a newly delivered unit starts on a simpler setup screen. The reviewer records both states and labels the demonstration appropriately. No device was powered on or tested for this example.

The final campaign must not describe the dashboard as the out-of-box screen unless the merchant verifies that claim. If the demo data look like actual measurement, clarify the sample status or choose a different real view. Stop when the setup route cannot be documented instead of inventing plausible instructions.

Keep interface truth separate from scene styling

Lighting and background can change for a campaign, but meaningful interface content should remain tied to the actual source. Check visible labels, numerical values, and icons after generation. A faithful body around a false screen still misrepresents the product, even if its physical shape passes review.

Itemlume creates visual assets and text briefs; it does not connect to devices, test screen functions, or validate accounts and subscriptions. Use the merchant’s confirmed records and an external edit if precise interface insertion is needed. Stop approval when the delivered default or demonstration conditions remain unknown.

Screen-state evidence map

Use this matrix as a manual review record and add your own real evidence. Its conditions are not completed test results.

Download this question’s review worksheet (CSV)