WeWeb: in development

Live virtual try-on for WeWeb: coming soon

WeWeb apps often sit on a separate backend that holds the product catalogue. The try-on is planned to need only the product image your page already shows, whatever backend it comes from. It is in development; today, WeTryOn runs on Shopify only.

Can you use it on WeWeb today?

Not yet. WeTryOn runs on Shopify today. A drop-in script for WeWeb is in development, with no date set. Join the list and we'll email you when it's ready.

How it will work on WeWeb

1. Add the script

The plan is one script added through WeWeb's custom code settings for your project.

2. Bind the product image

Bind the button's image to the same field your product page already displays, from your backend or API.

3. Shoppers try it on

The button opens the same live try-on Shopify stores use, with the camera notice first.

What to know about WeWeb

Any catalogue backend

Because the try-on needs only an image URL, it shouldn't matter whether your products live in Xano, Supabase, Airtable or your own API. Whatever your page binds to is what the try-on uses.

Single-page apps

WeWeb apps change pages without a full reload. The script is planned to notice when a new product appears, so the button stays in step as shoppers browse.

Self-hosted exports

If you export your WeWeb app and host it yourself, the script would be included in the export like any other custom code.

Virtual try-on on WeWeb: questions

When will WeTryOn be available on WeWeb?

We haven't set a date. We'd rather tell you when it works than promise a date we might miss. Join the list and we'll email you once.

Which backends will work with it?

Any that gives your WeWeb page a product image URL. The WeWeb version is planned to read only that image, not your database.

Will it keep up with page changes in a WeWeb app?

That is the plan: the script would watch for a new product on the page, since WeWeb apps change pages without reloading.

Will it work in an exported WeWeb project?

It should, since it is planned as ordinary custom code that travels with the export.