Localization & AR
Languages
Section titled “Languages”The embed ships in English, Turkish and Russian. Set the language per instance:
<togenar-embed project="…" configurator lang="tr"></togenar-embed>lang (alias: locale) controls the built-in option panel, the configuration summary and
all viewer chrome. It does not touch your page — mixed-language pages are fine.
AR opens directly in the browser — no app install:
| Device | Technology |
|---|---|
| iPhone / iPad | iOS Quick Look (USDZ) |
| Android | Scene Viewer (GLB) |
| WebXR-capable browsers | WebXR session |
The built-in panel includes an AR button. To trigger AR from your own button instead:
document.getElementById('view-in-ar').addEventListener('click', () => { tg.enterAR();});Call enterAR() from a real click handler — starting a WebXR session may require an
in-page user gesture per the browser’s activation policy. AR must be enabled on the
workspace plan.
Multi-part configurations
Section titled “Multi-part configurations”A configured product with several parts ships to AR as one merged model matching the shopper’s exact selection — not a pile of separate files.
Desktop: QR handoff
Section titled “Desktop: QR handoff”Desktops don’t do mobile AR — hand the session to the phone with a QR code:
const { ok, url } = await tg.getQr(); // PNG data-URL, encodes the short share linkif (ok) qrImg.src = url;Scanning opens the device-adaptive launcher with the current configuration intact, and the shopper continues straight into AR on their phone.
