What does a motion design deliverable actually look like?
Deliverables vary by format and purpose. A microinteraction might be a Figma prototype with timing annotations plus a Lottie JSON file. A state machine for a complex onboarding flow might be a Rive file with named states and transition logic. A set of CSS transitions might be delivered as a spec sheet with named tokens and code snippets. Every deliverable includes a written spec covering trigger, duration, easing, and the reduced-motion fallback.
How does handoff to our engineering team work?
We agree on your preferred format at the start of the engagement — Lottie, Rive, or CSS/JS specs. Files are delivered with accompanying documentation that covers implementation notes, trigger conditions, and fallback behaviour. We also offer a short handoff session with your engineers to walk through anything that needs context. Animation tokens are structured to integrate with your existing design token system where one exists.
How is motion design priced?
Pricing depends on scope: the number of animated states, the complexity of interactions, the output format, and the level of engineering collaboration required. Project-based engagements are scoped and quoted after an initial brief review. Retainer arrangements are agreed as a monthly capacity. We provide a clear scope document before any work begins so there are no surprises mid-project.
How do you handle accessibility — specifically prefers-reduced-motion?
Every animation that carries meaning or affects layout includes a prefers-reduced-motion alternative as a standard part of the deliverable. This might mean a cross-fade instead of a translate, an instant state change instead of a timed transition, or removing a looping animation entirely. Accessibility compliance is part of our definition of done, not a separate audit you need to commission.
What is the 60fps target and why does it matter?
Animations that drop below 60 frames per second feel janky — users notice even when they cannot name the cause. We design and test animations to maintain 60fps on mid-range devices, avoiding properties that trigger expensive browser repaints (such as width, height, or top/left) in favour of transform and opacity. For Lottie files, we agree a file-size budget per animation to protect page load performance.
When should we choose an agency over a freelancer?
A freelancer works well for a single, isolated deliverable with a clear brief. Choose an agency when motion needs to be consistent across a product or design system, when you need engineering collaboration built into the process, or when the scope is large enough that a single person would become a bottleneck. An agency also provides continuity — if a project extends or scope changes, the team absorbs it without restarting a hiring process.
Which animation formats do you support — Lottie, Rive, or CSS?
We work with all three. Lottie (JSON exported from After Effects via Bodymovin) suits illustrative animations and brand moments. Rive suits interactive state machines — loading spinners that respond to data, onboarding flows with branching logic. CSS and JS animation specs suit UI transitions and microinteractions that are better owned directly in code. We recommend a format based on your use case and your engineering team's stack, not on what is easiest for us to produce.