The White Lotus WebAR | Aydar Nuriev

Overview

A browser AR experience that records and encodes a shareable MP4 on the device. I worked on client-side capture and WebAssembly encoding for The White Lotus season 3 Reveal My Aura campaign across Max and Verizon retail.

I worked as part of a TVGla team that included design, production, content, and engineering.

The brief

Create a browser AR experience that produces a shareable video for The White Lotus season 3 campaign.

What I built

I worked on client-side capture and WebAssembly MP4 encoding across Max and Verizon retail versions.

The result

The browser produces a shareable MP4 on the device without a server-side rendering queue.

Desktop browser capture of The White Lotus Reveal My Aura experience with campaign branding visible — Desktop browser capture · official QR entry gate

Mobile browser capture of The White Lotus Reveal My Aura experience with its full campaign framing — Mobile browser capture · official experience

Final Reveal My Aura campaign share art for The White Lotus streaming on Max — Campaign share output

Live mobile Reveal My Aura quiz start screen for The White Lotus with the Start button visible — Live mobile browser capture · quiz start screen · August 2026

My engineering work

In-browser MP4 recording via WASM mp4-muxer
No upload or server-side rendering queue
Shareable video output from a mobile web page

A-Framecanvas-recordmp4-muxer (WASM)Webpack

Build details

Visit live site

These are live browser entry captures from August 2026. The desktop audit reached the entry screen without accepting camera permission, so camera tracking and physical-device performance are not claimed here.

CameraA-Frame runs the browser AR experience and requests camera access on the device.
Canvas captureThe client captures the rendered canvas during the experience.
WASM muxingmp4-muxer runs in WebAssembly to package the recorded frames as MP4 in the browser.
Share outputThe completed MP4 is produced on the device, without a server-side rendering queue.

My roleClient-side capture and encoding: I worked on the browser capture path and WebAssembly MP4 encoding with the TVGla team.
Runtime boundaryCamera, canvas, and MP4 stay in the client: The experience uses device camera access and canvas capture, then packages the result with mp4-muxer in WebAssembly.
What the captures showProduction browser states: These are browser captures of the live experience and its alternate entry state; they do not reproduce the camera interaction or generated video.