All there is to know about the benefits of the new version
Automatic synchronization directly with EAN and barcodes
Go further: We renamed the `sku` initialization parameter to `frame`. Both the `frame` parameter and the `setFrame` method of the VTO instance accept a free string representing indifferently an EAN, a UPC or a SKU, and it is now the module's job to find the corresponding asset.
Live display of the Virtual Try-On button on available frames
When a new frame of your catalog is available for try-on, an instant API call will allow you to set up the automatic display of the VTO button on the product page. Say goodbye to the message "this frame is not available for try-on" when clicking on an unavailable frame.
Go further: We recommend to call the `availability` endpoint when loading any page offering a VTO experience to correctly enable the CTA button only for frames that are available. This endpoint can be called with one frame (e.g. a product page) and up to a 100 frames at once (e.g. a catalog page).
An enhanced face tracking
Thanks to greater number of detection points, the glasses will better follow the movements of the user's face.
An improved overall performance
The core has been reworked to be more efficient.
Additionally, the Virtual Try-On offers a new way to be integrated, with an early pre-loading and then a start on the click of the CTA button.
Combined, the loading time can be reduced by up to 50% (depending on the integration).
Go further: We recommend to instanciate the module (with `createWidget`) as soon as possible in the lifecycle of the page. This will fetch needed data such as libraries and the frames and initialise our engine. Then, on the click of the CTA button, start the module (with `startVto`) to open the camera stream, start the protocols and start the VTO experience.
Bad network feedback
A specific alert message in the VTO module interface informs the user that a high latency is affecting the user experience, for instance while detecting the user and downloading the frame.