That’s the first question that arises once you drag a file to upload without hearing from the screen.
When technology runs too fast, the human brain feels disconnected. If a user drags a file into an app and it disappears into the cloud in 0.05 seconds with zero feedback, they don't feel efficient, THEY FEEL CONFUSED.
Real speed is about perceived speed. You need a micro-interaction to give the brain that essential fraction of a second to register success.
Now tell me, does using an animation file replacing that 0.05 seconds with a minimum 5 other seconds to deliver a perceived speed feeling make sense? It must be lightning fast to load the animation alone, without mentioning its reaction time!
That’s why Rive solves this better than traditional video loops:
No Fixed Timelines: The animation dynamically scales to real-time network response rather than forcing a 2-second video loop.
Instant State Snapping: If an upload finishes in 5ms, the state machine smoothly snaps directly into a satisfying success checkmark.
Data-Bound Triggers: Reacts directly to uploadProgress or isComplete inputs with microscopic asset overhead.
This week I worked on something really cool with Awesomic: the motion launch film for Supernova.
The idea came from their team. My job was to bring it to life and I had about 30 hours to do it. The one rule: no fake interface. Every screen in the film was captured straight from the real app, which made it harder and a lot more fun.
Huge thanks to the Awesomic team for the trust and to Miguel Saporetti for jumping in on motion.
Direction, AI & 3D: Ivam Marchon
Motion: Miguel Saporetti
Client: Awesomic
Making pixels dance is easy. Making them sell a vision is the real work.
Most people think fish can’t walk and horses don’t run through fire. But when you marry unhinged AI imagination with precision motion design, rules stop existing.
Did the motion hit or was it too fast? Be honest in the comments.🐟