Cavalry, the 2D motion-design application built around procedural workflows, continued to mature this year as an alternative to purely keyframe-driven animation. Where traditional motion graphics means hand-animating properties one at a time, Cavalry pairs a familiar timeline with a procedural node system — so a designer can drive animation with rules, math, randomness, duplicators, and live data instead of setting every keyframe by hand. It brings the generative mindset that runs through creative coding into a visual, designer-friendly tool, and it’s increasingly a bridge between the two worlds.
Watch: Getting Started — Your First Scene in Cavalry (YouTube)
Procedural thinking without writing code
The core shift Cavalry encourages is thinking in systems rather than individual movements. Instead of animating a hundred shapes by hand, you define behavior once — a rule for how elements distribute, respond, stagger, or react to a value — and the software generates the rest. Randomness and dynamics add organic variation; data connections let a chart or a title sequence update itself from a spreadsheet. It’s the same conceptual leap this site covers on the code side with tools like Processing and p5.js, but expressed through nodes and a timeline, so designers who don’t write code can still work generatively.
Where it sits in the toolkit
Cavalry occupies a useful gap: more generative and rule-based than a conventional keyframe animation tool, but more design-and-render-oriented than a node environment like TouchDesigner or Cables (which lean toward real-time and interactive systems). For designers producing motion graphics, data-driven visualizations, and stylized animation, it offers the expressive power of procedural generation while keeping the finished-render, layout-focused workflow their work demands. That makes it a natural on-ramp for motion designers curious about generative art — and a fast production tool for creative coders who’d rather not build everything from scratch.