# IMERZA

Ruslan Vasylev: Principal Engineer · Immersive Web (contract), From Oct 2025.

Help sales agents guide buyers through property and unit options in 3D.

As Principal Engineer for IMERZA, I built the web viewer and worked across the back-end and art teams to connect it with property sales applications. Sales agents use an iPad to guide buyers through property views and unit options displayed on a TV. My work brought content, loading, rendering, interaction, and reliability together into that sales workflow.

- Operator: Sales agent operating the iPad controls
- Audience: Buyer watching the property rendering and unit selection on a TV
- Ownership: Whole web viewer · product integration · content tooling
- Workflow: Prepared property content → sales-agent iPad controls → TV rendering and unit selection → buyer discussion

## Projects

- **Property sales web viewer**: Facts: Web viewer, Desktop · TV · iPad, Startup memory pressure.

## How does the viewer connect to the sales application?

### Web viewer

Ownership: Whole web-viewer architecture, product behavior and integration

I led the web viewer’s architecture, product behavior and application integration, building on an early rendering prototype. It supports sales agents guiding buyers through property views.

- Three.js · browser rendering
- Property scenes · development and unit views
- Architecture · viewer packaged for reuse in an Nx workspace

Technologies: Three.js, WebGL, Nx, GLB

### CMS + application state

Ownership: CMS/application-to-viewer state and events

I connected property content and the sales agent’s selections to scene configuration, camera presets, unit highlighting and filters shown to the buyer.

- Property content → scene configuration
- Sales-agent unit selection · camera presets · highlighting
- Filter events ↔ viewer state

### Desktop · TV · iPad

Ownership: Cross-device input and display integration

The sales agent operates the iPad controls while a more powerful rendering machine drives the TV. The buyer watches the property and unit views as the agent guides the conversation; interaction state travels between the devices.

- Sales agent operates the iPad
- Buyer watches rendering and selected units on the TV
- MQTT interaction state · device-appropriate rendering budgets

Technologies: MQTT

## How did assets reach the browser?

### Art-team preparation

Ownership: Art-team asset-preparation tooling

I wrote Blender scripts to help the art team prepare content for the engine, and worked on the conventions that make ingestion predictable.

- Blender scripts · repeatable asset preparation
- Export conventions · naming · ingestion expectations
- Prepared content → browser viewer

Technologies: Blender

### Gaussian splats

Ownership: Gaussian-splat scene integration

I integrated splat content into the browser experience and fitted it to the loading and rendering constraints of the device.

- Captured surroundings + modeled property assets
- Loading · detail · GPU resource budgets
- Dataset size ≠ resident data ≠ drawn splats

## How were loading failures fixed?

### Startup memory pressure

Ownership: Viewer loading and resource-lifetime fixes

I traced the loading failures to avoidable startup memory pressure. We changed allocation timing, limited concurrent texture work and corrected resource lifetimes while preserving rendering quality.

- Symptom · scenes fail during loading
- GPU diagnostic buffers · allocate when needed
- Lightmaps · bound simultaneous loading
- Textures · guard fallbacks · release unused resources

### Rendering regression checks

Ownership: Rendering-regression and device validation

The merged fix passed regression and live desktop Chrome checks with the rendering settings preserved.

- Merged loading fix
- Regression tests + live desktop Chrome checks passed
- Rendering settings preserved

## Where did I make engineering decisions?

### Across the product boundary

Ownership: Whole web-viewer delivery and application integration

My principal work spanned the whole viewer experience: technical decisions, product integration and validation of the result sales agents use.

- Technical decisions · integration · review · validation
- Rendering code ↔ application behavior ↔ art workflow
- Customer task · sales agent guides a buyer’s property discussion