Service 03 / 14
Motion & interaction design
Most sites have no motion design, only animations added page by page. We design a few movements and use them everywhere.
Symptoms
Signs the motion was never designed
- 01
Each page animates slightly differently.
- 02
Scroll effects hijack the scrollbar.
- 03
Elements jump as they animate in, or the page stutters.
- 04
Nobody has decided what reduced motion should look like.
Our approach
How we design motion
We start with four durations, two easing curves and a few patterns for entering, leaving, revealing and responding. Every animation draws on that list, so the site feels whole.
Each pattern gets its reduced-motion version the day it is designed, usually an appearance or cross-fade instead of movement.
Pieces
What we design and build
-
Motion tokens
Durations and curves as code variables, documented beside the components.
-
Scroll sequences
Pinned or stepped storytelling that follows native scrolling.
-
Page transitions
Continuity between pages with the View Transitions API, plain navigation where unsupported.
-
Feedback
Hover, press, focus, loading and success states that confirm what happened.
Handover
What your team gets
- Motion principles and tokens
- The patterns, built and in use
- A written reduced-motion specification
Work
Projects built with it
Products, prototypes and demo builds the studio made itself, each labelled with its status. None is client work.
-
PropertyTwin
A live marketing site for a property digital-twin service, built around a 3D sample villa that visitors orbit, open room by room and relight in the browser. : PropertyTwin -
ClinicJourney
The marketing website of a pre-launch patient-journey platform for aesthetic clinics, with an interactive walkthrough of one fictional patient across eight steps. : ClinicJourney
Stack
Tools we reach for
- CSS animations
- View Transitions API
- GSAP
- IntersectionObserver
- WebGL
How we build it Motion is set per page type on a scale from 0 to 3, gives way to reduced-motion settings and can be paused from every footer. How this site is built
FAQ
Questions about this
Won’t WebGL make the site slow?
It can, which is why it loads after the content, draws less on weaker devices, stops when it is off screen and becomes a still image for people who prefer reduced motion. The page works without it. How we budget for it.
Is accessibility included?
Yes, it’s part of every project. We work to WCAG 2.2 AA and test with automated checks, the keyboard and a screen reader.
Can you just design, or just build?
Yes, either. If we build from your designs, we’ll point out anything that will be slow, inaccessible or hard to maintain before it’s built, not after.
Want motion that explains something?
Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.

