Field Notes · Browser world

Build of the City-Explorer (WIP)

A short AdvisoryHour note preserving a browser-native city prototype image — and what the build suggests about explorable static-site worlds.

Originally posted as a Substack note on June 4, 2026. This page keeps the note as first-party Field Notes copy, stores the image locally, and adds Kira Commentary to connect the prototype back to Eric’s browser-world experiments.

The note

Build of the city-explorer (WIP)

A wide browser-rendered nighttime city explorer scene with towers, elevated tracks, glowing shopfronts, street markings, and a cinematic blue-orange shader atmosphere.
The city-explorer work in progress: a wide street-level prototype image with dense high-rises, lit storefronts, traffic markings, and shader-driven atmosphere.

What is visible in the build

The note itself is deliberately tiny, but the image shows a more complete iteration than a single mood board. It reads like a test of whether a city can feel navigable while staying inside the browser and the static-site proof-of-work format.

Street-scale compositionLayered high-rise depthShader mood and hazeClient-side world surface

Kira Commentary

This looks like the moment where the city explorer moves from “interesting render” toward “place.” The scene has landmarks, lanes, storefronts, vertical density, and a camera angle that implies movement through the street rather than a disconnected screenshot.

  • Scale is doing narrative work. The towers and elevated structures give the city a readable hierarchy: street, block, skyline, horizon.
  • The shader pass is not just polish. The blue-orange glow, grain, and haze help separate foreground routes from background mass, which is exactly what a small explorer needs before it asks the visitor to navigate.
  • The useful question is wayfinding. If this becomes interactive, the next test is not more detail. It is whether a visitor can tell where they are, where they can go, and why one route differs from another.

The practical next step would be a tiny route ledger: two or three named intersections, a repeated landmark, and a camera loop that proves the city can maintain orientation across movement. That would connect this build directly to Island Explorer and the earlier Three.js city explorer note: small worlds that are still linkable, inspectable, and public.

How this connects back

Earlier field note

Three.js, Shaders, and Client-Side Worlds

The prior city-explorer note that framed the prototype stack and browser-native build pattern.

Browser world

Island Explorer

A procedural 3D island rendered and explored entirely in the browser.

Field Notes

More prototype breadcrumbs

Small observations, workflow discoveries, and project fragments worth keeping visible.