A Gallery You Walk Through In A Browser

A collection only works in a room. Photographs of a room are not the room: scale disappears, the sequence the work was hung in disappears, and so does the part where you choose what to walk up to. The usual substitute is a grid of thumbnails, which answers none of that.

Put the visitor inside the space, on whatever device they already have, with nothing to install.

A walkable exhibition built with three.js and WebGL: a room with work hung at eye level, wall labels beside each piece, a title wall, and a doorway through to a second room. It runs in a browser on a phone. It is served from this site at /gallery.

The room is real geometry rather than a panorama, so a visitor moves through it instead of pivoting inside a photograph. Everything is keyed off one exhibition description, so hanging a different show is a data change rather than a rebuild.

Eric built the gallery engine, the room, the hanging system and the interaction. The exhibition currently running in it is his own demonstration show, and it is labelled as a demo. The engine's first outing was a client exhibition; that engagement is undocumented here because it is the client's to disclose, not his.

The device it has to run on. A 3D room is easy on a desktop with a graphics card and hard on a phone browser that a visitor opened from a link, and a phone is what most people will use. That is a budget, not a feature: the geometry and the textures are sized so the room loads and moves on a handset rather than so it looks best on a workstation.

Results from client deployments are shared with permission on a call.

The engine outlived the show. Keeping the room and the exhibition in separate layers meant that when the original show came down, what remained was a reusable piece of software rather than a dead site, and rehanging it was a change to a data file.

• three.js
• WebGL
• React
• Vite
• Vercel

• EricVegas.com Identity And Evidence Infrastructure