The carousel solution nobody asked to be this effective
I built this animation for negativo.es using a simple carousel.
Which, to be clear, is not the kind of sentence people usually say with pride.
The goal was painfully modest: show how a few screens work without turning the explanation into a second product experience.
No layered interactions.
No dramatic motion system.
No “let’s make the preview feel premium” detour.
Just a few screens, in order, doing what they already do.
Suspiciously reasonable.
The problem
When you want to show a small app flow, there’s always a temptation to overproduce it.
Not because the product needs it.
Because your brain, after enough hours looking at UI, starts inventing work.
Maybe it needs a more advanced transition system.
Maybe each screen should animate independently.
Maybe the whole thing should feel more alive.
Maybe, and this is always a bad sign, it should feel cinematic.
What I actually needed was much less glamorous:
Open the thing
See a few screens
Understand the app
Move on with your life
So I used a carousel.
The deeply offensive effectiveness of simple things
That was the whole trick.
A few screens.
A simple sequence.
Enough movement to make it readable.
Not enough movement to become the main character.
And annoyingly, it worked.
It worked because the point of the animation was not to impress anyone. It was to remove friction. To give a quick sense of the product without asking the viewer to decode a miniature interactive spectacle first.
Which is, unfortunately, what simple solutions tend to do when left unsupervised.
What I did not do
For the sake of my remaining dignity, here is a partial list of things I did not add:
Elaborate transitions pretending to add meaning
Fake device choreography
Prototype theater
Small flourishes whose main purpose was making me feel involved
Any attempt to turn “look, these are the screens” into a launch trailer
The carousel handled the job with the enthusiasm of office lighting.
Reliable. Unremarkable. Correct.
Why it worked
Because the animation only had one responsibility:
Show the product clearly, quickly, and without asking for extra effort.
That’s it.
It did not need to be clever.
It did not need to be memorable.
It did not need to perform emotional labor on behalf of the interface.
It just needed to explain a few screens without becoming another thing to understand.
An upsettingly low bar.
And yet, apparently, the correct one.
The annoying lesson
Building Negativo.es has already forced me to accept several unpleasant truths.
One of them is that a lot of UI communication problems do not need a clever solution.
They need a clear one.
The animation was there to answer a very simple question:
What does the app look like when you use it?
And the answer, apparently, did not require a small festival of transitions and self-congratulation.
Final thoughts
So yes, I built the animation with a simple carousel.
Not because it was visionary.
Not because it was particularly innovative.
Not because I discovered a new frontier in product storytelling.
Because it was the simplest possible way to show a few screens working.
And, in a minor personal inconvenience, that turned out to be enough.
Negativo.es continues to be an excellent source of small product decisions that should feel embarrassing, but keep being right.
