State machines explained clearly
I had used Rive only for timelines. Building the like button state machine showed me how much logic can live in the file.
Browse
Design animations that respond to taps, hovers and app data, export them as Lottie or Rive files and run them on web and mobile
Created by Kenji Mori
Videos of animations are useful for presentations, but products need animations that run inside the app: a like button that bursts when tapped, an onboarding illustration that reacts to swipes, a loader that changes when data arrives. Lottie and Rive are the two most common ways to ship this kind of motion, and this course teaches both.
We start by understanding how each format works and when to choose it. Then you will build animations in both, export them and run them on the web, with notes for iOS, Android and Flutter.
You will build three production style pieces: an animated like button with a hover and burst state, an onboarding illustration that responds to the current step, and a loading character that switches between waiting, success and error states.
The course suits designers who already animate a little and want their work to ship, and front end developers who want to understand what designers hand them. Basic knowledge of After Effects helps for the Lottie section; the Rive editor is taught from the start. Rive plans and features change often, so I point to the current documentation where details depend on your plan.
Motion and 3D designer teaching Blender, After Effects and interactive animation for product work
I work as a motion and 3D designer for digital products. Most of my week is spent animating interface concepts, making product renders for landing pages and building small interactive animations that ship inside apps.
I started in graphic design, so I teach 3D and motion for people who think visually but find the software intimidating. We focus on the handful of tools and settings that do most of the work: modelling with modifiers in Blender, lighting and rendering with Cycles and EEVEE, the graph editor in After Effects, and state machines in Rive.
I keep projects small and finishable. You will not spend hours on a scene you never complete. Each course ends with pieces you can put in a portfolio or hand to a developer.
I had used Rive only for timelines. Building the like button state machine showed me how much logic can live in the file.
As a front end developer I finally understand what to ask designers for. The React lesson was short and practical.
The loading character is now the centrepiece of my portfolio. Bones and constraints felt approachable after this.
Seeing the same project in Lottie and Rive helped me choose for our app. The file size comparison was eye opening.
Rarely covered in animation courses. Reduced motion handling is now part of our checklist.
The support table advice saved me from designing effects that would never export. Optimising tips were solid too.
Good content, but the Rive editor had moved a few panels since recording. The concepts still applied fine.