What it is
A visitor lands on the studio page and scrolls. The camera flies from outside a scene into its interior, through the room, and on into the next one, with no cuts anywhere in the sequence. Six scenes, one continuous move, and scroll position is the only thing driving it. It is live at robonamix.com/inside-the-studio.
There is no 3D engine in this
Worth saying plainly, because a page that moves like this usually implies otherwise. No WebGL, no scene graph, no renderer running in the browser. The depth is baked into pre-rendered video long before anything reaches a visitor. At runtime the browser decodes frames and animates opacity and transform on plain elements, and that is the whole mechanism. The engine coordinating it is about 9kB compressed with zero dependencies.
The scenes themselves are AI-generated. A video model rendered each one from a prompt and a reference frame, and the provider's watermark is still in the corner of every frame on this page, which is why you can see it. That split is worth being exact about, because it is the difference between what a model made and what I did. The model produced six rooms. I chose the ladder they describe, directed the camera so each flight ends where the next one begins, wrote the scrub engine that ties the playhead to scroll position, decided the encode strategy that makes seeking survive a phone, and built the branch that never fetches a single clip when a reader has asked for reduced motion. Generated scenes are cheap now. The part that is not cheap is making six of them behave as one continuous move.
Which means the page has one cost, and it is media. There is no frame budget being spent on geometry, no device tier where the scene degrades into a slideshow because the GPU gave up. It gets faster by shipping better encodes, not by simplifying the world.
The six scenes are an argument
The flight walks a ladder: Spark, then Resident, then Contributor, then Earner. Someone arrives curious, gets a bench, starts contributing to builds that are not theirs, and ends up earning from what they make. The scenes carry that in props rather than captions. A first breadboard, then a shared workstation, then a print rig running a job, then a shelf of finished pieces, then the room past the shelf. The camera does most of the explaining, so the copy on the page can stay short.
Reduced motion is a branch, not a slower version
When a visitor asks for reduced motion, the clips are never fetched at all. The stills cross-dissolve instead. That is a real second implementation rather than a damped version of the first, and it has a side effect worth naming: the reader who wanted less motion also gets a much lighter page.
What you are looking at on this page
These six frames are stills. The card that brought you here is not: it loops a showreel, 1.6 seconds lifted from each of the six scenes so the whole flight goes past in under ten. That clip is a recording of the move, not the move. Scroll drives the real thing, and a loop that plays itself cannot reproduce the part where you are the one steering it. It stays put until the card is on screen, and a reader who has asked for reduced motion never gets it at all, which is the same branch the live page takes.
So if the interaction is the part you want to judge, go and scroll the real thing.
Robonamix is my own project, which is what the self-directed label above says. Nobody commissioned this. It exists because I wanted to find out how far a scroll cinematic gets without a 3D engine, and the answer turned out to be most of the way.
