The field guide to app animations is a list of a hundred small things you see in apps every day — the bounce when you pull a feed to refresh, the heart that bursts when you like a photo, the shimmer of a screen still loading. For each one I wrote down where it really came from and how it actually works. The lesson from making it wasn’t about animation at all. It was about how much of what we all confidently “know” about these famous little moments is just wrong.
Look it up before you build it
The rule was simple: nothing goes on the list from memory. For each animation I found the real facts — the actual speed, the real bounce, the true story of who made it and when. You can’t convincingly copy one of these from a vague feeling. You need the real number, and the real number is almost never the one you’d have guessed.
The corrections are the interesting part
Checking things changes them. Everyone remembers the little heart on Twitter replacing the old star — and half the people you ask will tell you it happened in 2016. It was 2015. And it wasn’t a smooth animation at all; it was a strip of 29 separate drawings flipped through in sequence, like an old cartoon. That’s why a faithful copy has to flip through frames instead of smoothly growing. That detail only exists because the memory got corrected first. Build from the wrong year and you’d have built the wrong animation to match it.
Say “nobody knows” when nobody knows
Some of these genuinely can’t be pinned down. Who first made the little “genie” effect where a window sucks down into the dock. Who first called a small pop-up notice a “toast.” I couldn’t confirm either, so I wrote down that we don’t know — instead of picking a good-sounding answer and stating it like fact. This matters more than it looks. A reference is only worth anything if it’s willing to admit where it’s guessing. One confident made-up fact and you have to start doubting everything else on the page.
A list that stays useful
What makes it more than a dead list is that each entry points at where I actually used it, so the reference and the real work stay tied together instead of drifting apart. The full thing is the field guide to app animations.