Interactive 3D & Product Configurators
Help buyers inspect and configure a product in 3D.
A rotatable model is useful when it answers a question: how parts fit, which option changes the design or where a component sits. We build interactive browser scenes around that decision, with clear controls, dependable product state and a usable alternative when 3D is unavailable.
DIRECT ANSWER
Wavect develops interactive 3D viewers, technical scenes and product configurators for the browser, connecting scene controls and valid configuration state to an existing website, application or commerce workflow.
Best for
- Products whose shape, assembly or options are hard to explain in flat images
- Teams with 3D assets that need an interactive, maintainable web experience
Consider another approach
- A static rendering with no interaction requirement
- Camera-based placement or a headset-first training experience
Choose the question the scene should answer
Start with a viewer, an annotated assembly or a configurator, depending on the task. Agree useful camera positions, selectable parts, measurements or explanations, and the reset behaviour. We prototype the interaction using representative geometry before polishing every surface. New or unsuitable models go through 3D Modelling. Placing an object in a camera view belongs to AR Development, which has separate device and permission requirements.
Give options a single source of truth
A colour change is simple until size, accessories and availability constrain it. We map valid combinations and the identifiers passed to the host application. The scene, selection controls and written summary must agree, including when a user changes a choice quickly or returns to a saved configuration. Your catalog remains the source for product records; Product Information Management owns changes to that broader data workflow.
Budget for the phone your customer uses
Agree representative devices, connection conditions and measurable load and interaction budgets. We review geometry, textures, draw calls and rendering resolution, then load only what the journey needs. The Three.js responsive rendering guidance illustrates the cost of excessive drawing-buffer resolution. Library choice, such as Three.js or Babylon.js, follows the required features and maintenance environment. Browser support, failed asset downloads and graphics-context loss need explicit behaviour.
Keep the decision available beyond the canvas
Provide labelled controls for the actions people need, with keyboard and touch paths that do not depend on a precise drag gesture. Keep option names, selected values and essential explanations in accessible HTML. Respect reduced-motion preferences and offer a non-3D route using images, descriptions and the same configuration choices. A fallback should preserve the user’s selection and next step, not leave an empty panel or a decorative screenshot.
Illustrative acceptance: configure one product variant
A buyer chooses a finish and then a size that makes one accessory unavailable. The interface explains the conflict, resolves it through the agreed rule and displays the same valid combination in the model and summary. Reloading restores the selected configuration. With 3D disabled, the buyer can make the same choice through the alternative interface. This is a proposed acceptance scenario, not a measured conversion claim.
Hand over the scene and the decision it produces
We define the host-page interface, configuration payload, content-update process and ownership of errors. Prices and order acceptance remain authoritative on the server; a visual selection must not bypass business validation. E-commerce Development owns checkout and order operations. Handover includes source code, asset references, dependency choices and deployment notes. Live sensor feeds need an explicit data integration scope; a 3D view alone is not an operational digital twin.
Questions before you start
A browser viewer or configurator can sit inside an existing website or web application. We agree browser and device support first. Camera-based AR and headset experiences are separate interaction modes with their own requirements.
Yes, through an agreed interface. We map product identifiers, valid selections and the data passed to the host. Pricing, availability, authorization and order validation remain owned by the relevant business system.
That depends on the question it helps customers answer. We define a hypothesis and useful events, such as completed configurations or product questions resolved. A pilot can test those signals; the presence of a 3D model is not a conversion guarantee.
We define that before implementation. A small fixed catalog may use a documented release process; frequent changes may need a content or product-data interface. Editable assets, rule ownership and a reproducible deployment are part of the agreed handover.
Plan your interactive 3D experience
Show us the product decision you want to explain, available models, configuration rules and the website or application receiving the result. Include the devices and browsers your users actually use.