Skip to content
Design

Designing flows instead of static pages

Treat the scroll as a timeline and choreograph what the user discovers next

March 4, 2025
By Manweba

Document-era websites were stacks of pages. Product experiences are sequences: curiosity → orientation → proof → action. Design the journey, then let scroll (or step) reveal it.

Scroll as timeline

Each viewport can behave like a beat—one idea, one mood, one ask. Trigger reveals slightly before content fully enters view so motion is underway when attention arrives.

Animate once on first reveal unless the story needs scrubbing. Replaying entrances on every bounce feels cheap and wastes frames.

Staggered in-view reveal

jsx
Loading code…

Parallax with brakes on

Depth cues help storytelling when layers move at different rates—background slower, foreground closer to 1:1 scroll. Overshoot those ratios and you get motion sickness, not immersion.

Drive parallax with transform only. Never animate top/left for scroll linkage.

Parallax discipline

  • Background moves less than foreground—depth, not a carnival ride
  • One parallax hero per page is usually enough
  • Respect reduced motion: offer a static composition that still reads
  • If the copy still works with layers locked, the effect is optional

Final thoughts

Flows win when every beat earns the next. Storyboard the sections on paper first; only then wire scroll, stagger, and scrubbing. If a flourish does not advance the journey, it is noise.

Motion building blocks

Simple pieces we compose into scroll stories

Live Preview
Fade In
CodeStep 1 of 4
Loading code…

Ready to build something this considered?