Insights
A house that builds itself while you watch

This post was meant to be called "a house that builds itself as you scroll." That was the plan for the hero of Ninebark, a sample builder's website: you scroll, the slab is poured, the walls go up, the roof closes in, and the lights come on. By the time I built it, on 14 November, the house built itself while you watched instead, and the page scrolled like any other page. This is why.
What a scroll scene is, and why I liked them
For most of this year, my favourite trick on a marketing page was the pinned scroll scene. The section sticks to the screen, and your scrolling, instead of moving the page, plays an animation: a product turns, a diagram draws itself, a video runs forwards and backwards under your thumb. It feels expensive. I have written about how to make it feel that way in scroll-scrubbed video that feels premium, and the technique works.
Browser makers are betting on it too. Scroll-driven animations are one of the focus areas of Interop 2026, the yearly effort in which Apple, Google, Microsoft and Mozilla agree to make a set of features behave the same in every browser. Mozilla's announcement, published 12 February 2026, says the feature "replaces heavy JavaScript solutions that run on the main thread," and the web.dev write-up the same day lists it among the year's priorities. The plumbing is getting easier every month.
The plumbing was never the problem.
What I saw
On 9 November, reviewing one of my own product pages, I wrote myself a note: many people still do not get the scroll scrub. Find a compromise that still animates, keeps the page easy to use, and lets the animations play on their own.
The trouble is simple to describe. Someone lands on the page, scrolls, and the page stops moving. The section has pinned, and their scrolling is now feeding an animation they did not know was there. To them, the site has frozen. Scroll harder and the story flies past in a second. The people who stop and enjoy it tend to be the people who build websites.
None of this was news to researchers. Nielsen Norman Group's guidance on taking over the scroll, written in 2023, concluded that it "leads to more user pain than benefits" and that "most usability issues observed on desktop were exacerbated on mobile." I had read that and decided my versions were the exception, because they were well made. Seeing my own pages misread is what changed my mind.
There was one more clue, from October. The scroll scenes on one of my sites looked broken on my own iPad. They were not broken. The iPad had Reduce Motion turned on, an accessibility setting, and the page was correctly holding still. I built those scenes, and I still could not tell correct from broken.
Three days after that note, I settled it for good: no full-screen scenes tied to scroll, anywhere. Same drawings, different clock.
The compromise: a stepper that plays itself
The replacement first went onto the overview page for Grow Your Clinical Practice the same day, 9 November, and it now runs every animated section there. I call it a stepper. It is a section one screen tall or shorter, holding a short numbered sequence. It plays itself, step after step, and the page around it scrolls normally the whole time.

The rules took a few rounds to get right, and each one exists because of something a visitor would otherwise trip on:
- It starts only when at least half of it is on screen. An animation that begins while you are still reading the section above is an animation you miss.
- It holds while a mouse rests on it, or keyboard focus is inside it. If you are reading step two, step two stays. On a touch screen a tap does not count as resting, so a tap never leaves it stuck.
- A step you pick stays picked. Tap a step, swipe sideways or use the arrow keys, and autoplay stops for good. Only the play button starts it again. Nothing is more irritating than choosing something and having the page change it back.
- Reduce Motion means it never plays itself. Every step is still one press away.
- It never moves the page. Every step is stacked in the same space, so the section is exactly as tall as its tallest step and nothing below it jumps.
Timing was the last thing I tuned. The stepper's default is slower, and on those sections it dragged. They now hold 3.8 seconds a step, which is long enough to read one line of copy and see the drawing finish.
The house, in four steps
Ninebark was built around a stepper from the start rather than retrofitted. Its hero raises a farmhouse in four steps, and each step is tied to a sample 34-week construction schedule so the numbers mean something to a homeowner: site, weeks 0 to 4; framing, weeks 4 to 14; envelope, weeks 14 to 24; and dusk, weeks 24 to 34, the finished house with its windows lit.

A hero gets more patience than a section further down, so each step here holds 6.5 seconds. When a step begins, a week counter in the corner runs up from the last step's number to the new one over 1.9 seconds while the camera glides to its next view. Tap the scene and it moves forward. Swipe and it goes either way. A play and pause button sits with the step buttons, and the clock stops whenever the hero scrolls out of view or the tab is in the background.
Reduce Motion gets a different opening, and I think it is the most considerate line in the file. A visitor who has asked their device for less motion does not land on a bare concrete slab and an invitation to press buttons. They land on the finished house at dusk, which is the picture the whole sequence is building towards anyway.
Under all of it is a quieter decision. The hero works with no 3D at all. It begins as four still images rendered from the Blender scene, swapping as the steps change, and only when the device has shown it can carry the live model does the 3D version take over the same four steps. How that model is made small enough to load on a phone is its own story, told in Blender to the browser.
What the scroll still does well
I have not given up on scroll as a storyteller. A long article that reveals its diagrams as you reach them is using scroll honestly, because the reader is already scrolling to read. The line I drew is narrower: the page must always move when you move it. If a section needs the visitor to learn a new gesture before it makes sense, it is asking them to work for my benefit.
For a builder, a clinic or anyone selling to the public, that line matters more than for a design studio. The person on their site is not there to admire the website. They want to know what the house will look like and how long it will take, and the stepper tells them both before they have finished their first scroll.
On Ninebark that answer is a farmhouse at dusk with its windows lit, and a week counter stopped at 34.
Common questions
What is a scroll-scrubbed or pinned scroll section?
A section that sticks to the screen while your scrolling plays an animation instead of moving the page. It can look impressive, but many visitors read the stopped page as a frozen site.
Does an autoplay animation annoy visitors?
It can if it starts off screen, runs while you are reading, or overrides your choice. The stepper starts only when half of it is visible, holds on hover or focus, and stops for good once you pick a step.
What happens if someone has Reduce Motion turned on?
The sequence never plays itself. On Ninebark the visitor opens on the finished house, and every step is still one press away.
Do I need 3D for a hero like this?
No. The Ninebark hero starts as four still images and works fully without 3D. The live model only takes over on devices that can carry it.
Related work
Related



