Glasses Virtual Try-on Widget

Are you looking for a way to revolutionize the eyewear shopping experience for your customers? Look no further than the Jeeliz VTO widget! It offers seamless integration into your e-commerce website or mobile application with just a few lines of code, allowing your customers to try on glasses virtually in real-time.

Imagine your customers being able to see themselves in the perfect pair of glasses before making a purchase, all from the comfort of their own home. With the Jeeliz VTO widget, this dream can become a reality. Say goodbye to the guesswork and uncertainty that often come with online shopping, and say hello to increased customer engagement, satisfaction, and loyalty.

You can find more information on Jeeliz Official website.

Table of contents

• Why it matters
• Features
• Demonstrations
  • Included in this repository
  • Demo app
  • They trust us
• Glasses 3D models
  • From GlassesDB
  • As a static file
• Documentation
• Misc
  • Test GlassesDB SKU availability
• Compatibility
• Optimization
• Hosting
• License

Why it matters

Here are the most important reasons why you should consider adding a virtual try-on feature to your eyewear e-commerce website:

1. Enhanced Customer Engagement and Experience: Virtual try-on technology allows customers to actively engage with your products and see how different frames look on their face. This interactive experience can increase customer engagement and satisfaction, leading to more informed purchase decisions and increased brand loyalty.

2. Increased Sales: Virtual try-on technology can increase sales by making it easier for customers to find frames that they like and feel comfortable wearing, leading to more purchases and fewer abandoned carts.

3. Competitive Advantage: Adding a virtual try-on feature can give you a competitive advantage over other eyewear e-commerce websites that do not offer this feature, leading to increased brand perception and customer loyalty.

Features

• real-time web based glasses virtual try on,
• light reconstruction (ambient + directionnal),
• very robust to:
  • lighting conditions (back light, side light),
  • facial variations (bearded people, hair partially covering the face, ...),
• works both on mobile (IOS, Android) and desktop,
• lightweight (2.1MB transferred for the demo including 3D models),
• high end 3D engine with:
  • physically based rendering (PBR),
  • raytraced shadows,
  • deferred shading,
  • temporal antialiasing.

Demonstrations

Included in this repository

• Static Integration demo (index.html of this repository)
• React/Webpack/NodeJS 12 Integration demo
• React/Vite/NodeJS 18 Integration demo

Demo app

• Jeeliz sunglasses web application (not included in this repository)

They trust us

• Lensway: you can test it here: Reverse - matte dark blue product page (click on Prova Digitalt button below the product picture). Following Lensway design guidelines, the rendering is very simplified (no lenses, no shadows, no too shiny reflections),

• Jean Paul Gaultier: You can test it here: Arceau Gold product page (click on the Virtual Try-on button). As a luxury brand, Jean Paul Gaultier is very attached to the realism of the rendering and the quality of the AR experience,

• Pardon!: You can test it here: sunglasses Trou de Fer (click on the VIRTUAL TRY ON button on the bottom right of the product picture). As the iconic fashion-wear brand from the island of Réunion, Pardon! need a high-quality graphic rendering to show the quality of the materials of their sunglasses, especially for the engraved wooden branches,

• Zeelool: you can test it here: Street-Artist product page (click on AR Try on on the top left of the product picture. They are still using a deprecated version of the viewer so the tracking jitters a bit).

Glasses 3D models

From GlassesDB

Glasses models are stored on the Jeeliz GlassesDB. Each model is identified by a unique SKU. You can check the different models available by opening glassesSKU.csv file.

If you want us to add specific glasses models to GlassesDB, please contact us at contact__at__jeeliz.com or here. We charge for this service.

As a static file

You can convert your own glasses GLTF 3D Model to a proprietary JSON file accepted by this widget using Jeeliz Glasses Studio 3D. You can download:

• The PDF documentation about GLTF models specs and how to import your model to Jeeliz VTO widget
• Some samples of GLTF glasses 3D models

You can use both models from GlassesDB and your own static models. Glasses Studio 3D is a free web application and you keep the IP on your exported 3D models. Unlike this widget, Glasses studio 3D works:

• Only on desktops, with a fullHD screen resolution (1920x1080),
• Your GPU device needs to be able to do MRT (Multi Rendering Targets) on at least 4 targets (i.e. it may not work on deprecated or very cheap hardware).

However, the capabilities of Glasses Studio 3D are below what we offer with GlassesDB. This is a comparison:

Documentation

This library relies on WebAR.rocks WebGL Deep Learning technology to detect and track the face using a neural network. You can find the technical documentation in doc.pdf.

If you need more help, we offer development services and customized support. You can contact-us here.

Misc

Test GlassesDB SKU availability

In some cases, SKU can be generated dynamically from the backoffice of the glasses e-commerce website. It can be <glassesMakerAsPrefix>_<collection>_<modelId>. We need to test if this SKU is in GlassesDB in order to display the Virtual Try-on button to the user. To do this, request with GET or POST method (using an XMLHttpRequest for example):

https://glassesdbcached.jeeliz.com/testSku/<skuToTest>

You can test it here:

• For existing SKU "rayban_aviator_or_vertFlash"
• For non-existing SKU "notASKU"

Compatibility

• If WebGL2 is available, it uses WebGL2 and no specific extension is required,
• If WebGL2 is not available but WebGL1, we require either OES_TEXTURE_FLOAT extension or OES_TEXTURE_HALF_FLOAT extension,
• If WebGL2 is not available, and if WebGL1 is not available or neither OES_TEXTURE_FLOAT or OES_HALF_TEXTURE_FLOAT are implemented, the user is not compatible with the real time video version.

If a compatibility error is triggered, please post an issue on this repository. If this is a problem with the camera access, please first retry after closing all applications which could use your device (Skype, Messenger, other browser tabs and windows, ...). Please include:

• a screenshot of webglreport.com - WebGL1 (about your WebGL1 implementation),
• a screenshot of webglreport.com - WebGL2 (about your WebGL2 implementation),
• the log from the web console,
• the steps to reproduce the bug, and screenshots.

If the user was not compatible or refuses to share its camera video stream, an image based fallback version was available til January 2020. The server side webservice generating the rendering has been undeployed. If the user does not want to share its camera or if its implementation of WebGL is too minimalistic, a FALLBACKUNAVAILABLE error will be triggered.

Optimization

If you meet some performance issues, please first:

• Check that you are using the latest main script ( /dist/jeelizNNCwidget.js ),
• Check that your browser is updated (Chrome is advised), check that your graphic drivers are updated,
• Enter chrome://gpu in the URL bar and check there are no major performance caveats, that hardware acceleration is enabled, that your GPU is correctly detected,

The performance is adaptative. We do as many detection loops per rendering till we reach a maximum value (7). If we cannot reach this value, the GPU will be running at 100%. The closer we are to this maximum value, the less latency we will observe.

So it is normal that the GPU is running at 100%. But it may be annoying for other parts of the application because DOM can be slow to update and CSS animations can be laggy.

The first solution ( implemented in Jeeliz sunglasses web-app ) is to slow down the glasses rendering once the user has clicked on a button using:

JEELIZVTO.relieve_DOM(<durationInMs>)

For example,JEELIZVTO.relieve_DOM(300) will free the GPU during 300 milliseconds.

If you need to slow down the rendering to free the GPU during an undertermined period of time, you can use:

JEELIZVTO.switch_slow(<boolean> isSlow, <int> intervalMs)

Where intervalMs is the interval in milliseconds between 2 rendering loops.

Hosting

This widget access the user's camera video stream through MediaStream API. So your application should be hosted by a HTTPS server (even with a self-signed certificate). It won't work at all with unsecure HTTP, even locally with some web browsers.

License

Jeeliz VTO commercial software license