A heavily animated product site that still runs smoothly
Scootrr
scootrr/overview.md
- Role
- Frontend engineer, animation and performance
- Timeline
- 3 weeks
- Team
- 1 designer, 1 developer
- Category
- Next.js

The challenge
Scootrr's site presents an AI-powered e-scooter safety system. The design called for advanced GSAP timelines, ScrollTrigger scenes, Lenis smooth scrolling and 3D animation on the same page, which is the kind of combination that easily makes a site janky.
How I solved it
1. One scroll engine
Lenis drives scrolling and GSAP ScrollTrigger reads from it, so animations and scroll never fight each other.
2. Animate only what is on screen
Scenes are created and paused as they enter and leave the viewport, so off-screen animation costs nothing.
3. Cheap properties and lazy assets
Animations use transforms and opacity, and heavy media loads only when its section is near.
architecture.txt
Lenis → smooth scroll
GSAP ScrollTrigger → scene timelines
3D animation → loaded and paused per section
Static Next.js site, no back end
- 3 weeks
- Delivered
- 3
- Animation engines working together: GSAP, ScrollTrigger, Lenis
What I learned
With this much motion, performance is a design decision made from the start. Limiting what runs at any moment mattered more than optimizing each animation.