Use Threekit Product Visualization to display products configured through Threekit Platform.
Threekit Platform owns product selections, configuration rules, validation, and pricing. Threekit Product Visualization owns the assets and visual behavior needed to represent that configuration. Your application connects the two through their APIs.
Responsibilities
| Component | Responsibility |
|---|---|
| Threekit Platform | Product configuration, available options, valid combinations, pricing, and quotes |
| Threekit Product Visualization | Models, materials, scenes, cameras, rendering, and visual attributes |
| Your application | Product and attribute mapping, API calls, and synchronization |
Keep business rules in Threekit Platform. Visual logic should translate the resulting configuration into scene changes, such as applying a material or displaying a component.
Map platform data to visual assets
The two systems have separate data models. Your implementation defines the relationship between them.
| Mapping | Purpose |
|---|---|
| Platform product → visual asset | Identifies which asset to load |
| Platform option → visual attribute | Identifies which attribute to update |
| Platform option value → visual value | Translates the selection into the value expected by the asset |
Identifiers, attribute names, and values do not need to match between systems. Define explicit mappings, including any unit or format conversions.
Some platform options have no visual effect. Map only the values required to represent the product.
Initialize the visualization
- Obtain the product and current configuration from Threekit Platform.
- Resolve the corresponding visual asset.
- Initialize the viewer and wait until its configuration interface is ready.
- Translate the platform configuration into visual attribute values.
- Apply those values through the Product Visualization Configurator API.
The Player and Configurator APIs provide the interfaces for controlling the viewer and setting visual attributes. In this integration, the Configurator API applies the visual representation; Threekit Platform remains responsible for product configuration and rules.
Apply configuration changes
Route changes to product selections through Threekit Platform before updating the visualization.
After the platform processes a change, read the resulting configuration and update the mapped visual attributes. Include dependent selections that changed as a result of the platform's rules.
Do not treat a successful visual update as product validation. The viewer displays the configuration; Threekit Platform determines whether it is valid.
If an interaction inside the visual experience changes a product selection, send that proposed change through the same platform workflow. Camera movement, zoom, and other viewing controls can remain local to the viewer.
Keep the viewer synchronized
- Apply updates in configuration order so an older response cannot overwrite a newer state.
- Avoid sending programmatic visual updates back to the platform as new user selections.
- Handle missing mappings explicitly instead of displaying an unrelated default.
- Retain the platform configuration if a visual update fails, then retry or reinitialize the viewer from that state.