Do I need to have a developer on board to be able to integrate the Viewer?
The Viewer is a technical product and its integration does require development skills. The integration is based on JavaScript and is quite lightweight. We estimate that a skilled developer could complete the basic Viewer integration within a day. So, essentially, yes, you need a developer with JavaScript knowledge to set you up, and it won’t take them more than a few days to have everything up and running. We recommend that you test everything out in a staging environment, and then push live once fully integrated.
Is the Viewer loaded in an iFrame? How long does the integration take?
The Viewer integration is not iFrame based, but a JavaScript component on your website. Integration time can vary on where it is being integrated and what systems need to connect to it in the background. A basic integration can be completed within a day, and including testing, setups and push live, we estimate not more than a few days.
How do we implement the swatch menu/configurator?
There is no set way to implement the swatch menu, or as we often refer it to as “the right panel”. However we do have an elaborate guide on optimizing right panel user experience. As for the technical implementation, please take a look at this example from the technical documentation:
Link: Viewer with multiple feature types
What naming convention/identifiers do you use for products and configurations?
We always implement a naming convention and structure that mirrors the customer’s setup. That means that you can keep using your internal IDs and SKUs when interacting with Cylindo APIs. We will be requesting all necessary information before starting production.
Are there characters I need to avoid in my identifiers for products, features and options?
Yes, there are a limited number of characters that are not supported. The character not supported is due to keeping the cache infrastructure as efficient as possible. The characters not supported are:
- Product code on a product can not contain % / * : ,
- Feature codes on a product can not contain colon % * ,
- Option codes on a product can not contain colon % * ,
- Default Material codes in a project can not contain % * ,
Can we use our own content in the 360 viewport?
Yes, the Viewport can support the display of external content and custom images that are not Cylindo content. You can combine content from different sources and show all that in the Viewport. This can also include videos hosted on channels like YouTube or Vimeo.
Can we show an image before the 360 sequence?
Yes, you can choose to do your integration in such way that before the 360 sequence is fully loaded, you can have a display of a static image in the viewport, which can replace the loading animation. This can be the first frame of the configuration, which makes a seamless transition between the first statis image and the 360 sequence.
What happens if we request a configuration you do not have?
If you request a wrong configuration or one that we have not created in Cylindo for that particular product, you will receive a 404.